﻿<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-chen-lsr-tl-02" ipr="trust200902">
 <front>
  <title abbrev="IGP TL">IGP for Temporal Links</title>
  <author initials="H" surname="Chen" fullname="Huaimo Chen">
   <organization>Futurewei</organization>
   <address>
    <postal>
     <street />
     <city>Boston, MA</city>
     <region />
     <code />
     <country>USA</country>
    </postal>
    <email>hchen.ietf@gmail.com</email>
   </address>
  </author>

<!--
    <author initials="B" fullname="Bruno Decraene" 
            surname="Decraene">
      <organization> Orange </organization>
      <address>
        <postal>
          <street></street>
          <city></city>
          <region></region>
          <country>France</country>
        </postal>
        <email>bruno.decraene@orange.com</email>
      </address>
     </author>

    <author fullname="Les Ginsberg" initials="L" surname="Ginsberg">
      <organization>Cisco Systems</organization>
      <address>
        <postal>
          <street>510 McCarthy Blvd.</street>
          <city>Milpitas</city>
          <code>CA 95035</code>
          <country>United States</country>
        </postal>
        <email>ginsberg@cisco.com</email>
      </address>
    </author>
-->

     <author initials="A" fullname="Aijun Wang" 
            surname="Wang">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street>Beiqijia Town, Changping District</street>
          <city>Beijing</city>
          <region> </region>
          <code>102209</code>
          <country>China</country>
        </postal>
        <email>wangaj3@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Gyan S. Mishra" initials="G" surname="Mishra">
      <organization>Verizon</organization>
      <address>
        <postal>
          <street>13101 Columbia Pike</street>
          <city>Silver Spring</city>
          <code>MD 20904</code>
          <country>USA</country>
        </postal>
        <phone> 301 502-1347</phone>
        <email>gyan.s.mishra@verizon.com</email>
      </address>
    </author>

  <author fullname="Zhenqiang Li" initials="Z" surname="Li">
    	<organization>China Mobile</organization>
    	<address>
        <postal>
          <street>No.32 Xuanwumenxi Ave., Xicheng District</street>
          <city>Beijing</city>
          <code>100032</code>
          <country>P.R. China</country>
        </postal>
        <email>li_zhenqiang@hotmail.com</email>
      </address>
    </author>

   <author initials="Y" fullname="Yanhe Fan" 
            surname="Fan">
      <organization>Casa Systems</organization>
      <address>
        <postal>
          <street></street>
          <city></city>
          <region></region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>yfan@casa-systems.com</email>
      </address>
    </author>

   <author initials="X" fullname="Xufeng Liu" 
            surname="Liu">
      <organization>Alef Edge</organization>
      <address>
        <postal>
          <street> </street>
          <city> </city>
          <region> </region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>xufeng.liu.ietf@gmail.com</email>
      </address>
    </author>

 <author initials="L" fullname="Lei Liu" 
            surname="Liu">
      <organization>Fujitsu</organization>
      <address>
        <postal>
          <street> </street>
          <city> </city>
          <region></region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>liulei.kddi@gmail.com</email>
      </address>
    </author>
<!--
    <author fullname="Donald E. Eastlake 3rd" initials="D" surname="Eastlake">
      <organization>Futurewei</organization>
      <address>
        <postal>
          <street>2386 Panoramic Circle</street>
          <city>Apopka, FL</city>
          <region></region>
          <code>32703</code>
          <country>USA</country>
        </postal>
        <phone>+1-508-333-2270</phone>
        <email>d3e3e3@gmail.com</email>
      </address>
    </author>
-->
  <date year="2024" />


  <abstract>
  <t>This document specifies extensions to OSPF and IS-IS for 
     temporal links whose costs are functions of time. 
   </t>
  </abstract>

  <note title="Requirements Language">
   <t>
    The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, 
&quot;SHALL&quot;, &quot;SHALL NOT&quot;,
      &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, 
&quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
      document are to be interpreted as described in
    <xref target="RFC2119" />
    <xref target="RFC8174" />
    when, and only when, they appear in all capitals, as shown here.
   </t>
  </note>
 </front>
 <middle>

  <!-- Introduction -->
  <section title="Introduction">

   <t>The cost of a link is normally a constant such as C forever 
      (i.e., from current time to indefinite future, 
      refer to <xref target="c-link-cost"/>) 
      when there is no change on the cost of the link.

      <figure anchor="c-link-cost" 
       title="Constant Link Cost">
          <artwork align="center"><![CDATA[  Link Cost 
    ^
    |
   C|______________________________________________________
    |
    |
   -+------------------------------------------------------> Time
    | ]]>
</artwork>
      </figure>
   </t>

   <t>However, there are some links in a network 
     whose costs are functions of time 
     (refer to <xref target="tl-cost"/>). 
     These links are called temporal links.

      <figure anchor="tl-cost" 
       title="Link Cost of Temporal Link">
          <artwork align="center"><![CDATA[  Link Cost 
    ^
    |                                    
    |                                C3___________
    |        C1__________
    |                                             
  C0|__________                                   C4_________
    |                  C2________________
    |
   -+-------------------------------------------------------> Time
    |T0        T1        T2              T3         T4]]>
</artwork>
      </figure>
</t>

   <t>This document proposes extensions to IGP (i.e., OSPF and IS-IS)
      for distributing cost functions of temporal links and
      handling temporal links. 
      Every node in the network computes the shortest paths
      using the costs of temporal links based on the cost 
      functions.</t>

  </section> <!-- Introduction -->



  <section title="Temporal Link Cost Functions">

   <t>This section illustrates a few temporal link cost functions 
      through an example. </t>

    <section title="Example Network with Temporal Links">
     <t><xref target = "net-tls"/> 
        shows an example network topology containing temporal links.
 Nodes Sa, Sb and Sc are satellites in a first orbit. 
 Nodes S1, S2 and S3 are satellites in a second orbit, 
which is adjacent to the first orbit. 
Nodes A and B are the nodes on the earth each with a ground station 
seeing or connecting a satellite.

A satellite has links from it to its adjacent satellites. 
These links are stable. 
The costs of these links are not changing typically. 
For example, node Sa has links from Sa to Sb and S1; 
node Sb has links from Sb to Sa, Sc and S2. 
These links are stable. </t>

     <t>A satellite moves around the earth in its orbit. It moves around 
the earth once in a period. 
For example, a starlink satellite moves around the earth once 
every 95 minutes (i.e., 5,700 seconds). 
During this period, the satellite can see or have link from it to 
a node on the earth in a time interval. 

For example, the time interval is 398 seconds for a starlink 
satellite. During each period, a satellite can see or have a link 
from it to a node on the earth for a time interval. 

For example, when node Sa is a starlink satellite, 
node Sa has a link from Sa to A for a time interval 
such as 398 seconds every period such as 95 minutes 
(i.e., 5,700 seconds), node A has a link from A to Sa for the time 
interval such as 398 seconds every period such as 95 minutes 
(i.e., 5,700 seconds). 
Similarly, for the links between Sb and A, Sc and A, 
S1 and B, S2 and B, and S3 and B.
</t>

    <t>
<figure anchor="net-tls" 
 title="Network with Temporal Links">
  <artwork  align="center"> <![CDATA[                  \               \
                    \               \
       - - - - - - [ Sa ]----------[ S1 ]  - - - - - - - - - -
      /               \               \                       \
     /                 \               \                       \
    /                   \               \                       \
 [ A ] - - - - - - - - [ Sb ]----------[ S2 ]  - - - - - - - - [ B ]
    \                     \               \                     /
     \                     \               \                   /
      \                     \               \                 /
       -  -  - - - - - - - [ Sc ]----------[ S3 ]  - - - - - -
                              \               \ 
                               \               \]]></artwork>
</figure>
</t>

    <t>The link between a satellite node and a node on the earth is 
laser or microwave. The quality or cost of the link is affected by 
weather conditions. In a cloudy condition for a time interval, 
the link bandwidth is reduced. 
When Bw is the bandwidth of the link in an ideal weather condition, 
Bw is reduced to P*Bw in a cloudy condition, 
wherein P is a percentage such as 50 percents. 
When the cost of the link is C in the ideal condition and 
is calculated using a reference bandwidth, 
the cost of the link is increased to C/P in the cloudy condition 
in the time interval. When P = 50 percents, 
the cost of the link is increased 
to 2C (= C/0.5) in the time interval. 
</t>

    </section>

<!-- Example Network with Temporal Links -->

    <section title="Periodic Cost Function">
<!--
    <t>By default, the cost of a link from A to B is calculated by 
dividing the reference bandwidth by the link bandwidth. 
For example, suppose that the reference bandwidth is 10 Gbps, 
the bandwidth of the link from A to B is 1 Gbps, and the cost 
of the link from A to B is 10 Gbps / 1 Gbps = 10. 

A configured cost of the link from A to B will overwrite the 
calculated cost of the link.</t>
-->

   <t><xref target = "tl-cost-periodic"/> shows an example 
of a periodic temporal link cost function 
(or periodic cost function for short). 
The cost of a temporal link such as link from A to Sa is 
C0 for a time interval such as 400 seconds
from a given time T0, in every time period such as 95 minutes 
(i.e., 5,700 seconds). 

When the given time T0 is now, 
the cost of the link is
C0 for 400 seconds and then Infinity for 5,300 seconds
in every 95 minutes (i.e., 5,700 seconds). 

That is that the cost of the link is C0 from now for 400 seconds, and 
then Infinity for 5,300 seconds (i.e., the rest of the first 95 minutes); 
C0 from 95 minutes later for 400 seconds 
and then Infinity for 5,300 seconds (i.e., the rest of the second 95 minutes); 
C0 from 2x95 minutes later for 400 seconds 
and then Infinity for 5,300 seconds (i.e., the rest of the third 95 minutes);
and so on. 

      <figure anchor="tl-cost-periodic" 
       title="Periodic Temporal Link Cost Function">
          <artwork align="center"><![CDATA[  Link Cost 
    ^
    |                                                 C1 = Infinity                                
    |    C1_____________     C1_____________     C1_____________
    |
    |                                                 
  C0|______            C0______            C0______
    |                    
    |
   -+---------------------------------------------------------->Time
    |T0    T1           T2     T3           T4     T5
    | 400s |<- 5,300s ->| 400s |<- 5,300s ->| 400s |<- 5,300s ->|            
    |<-- 95m(5,700s) -->|<-- 95m(5,700s) -->|<-- 95m(5,700s) -->|]]>
</artwork>
      </figure>
</t>

    </section>
<!-- "Periodic Cost Function" -->

    <section title="Change in Given Periods">
     <t>The cost of a temporal link is
C0 for a time interval in every time period except for some given periods. 
In each of the given periods, the cost of the link is
C0', for example, C0' = 2*C0.</t>

     <t>When given periods are two periods from given time T0' 
as shown in <xref target = "tl-cost-given-periods"/>, 
for each of the two periods from time T0', the cost of the link is C0' 
for 400 seconds for the period (95 minutes from T0' or 95 minutes from T2') and
then Infinity for the rest of the period. 

In the first given period (i.e., 95 minutes from T0'), 
the cost of the link is C0' from T0' for 400 seconds and 
then Infinity for 5,300 seconds (i.e., the rest of the first given period);
in the second given period (i.e., 95 minutes from T2'),
the cost of the link is C0' from T2' for 400 seconds and 
then Infinity for 5,300 seconds (i.e., the rest of the second given period).

      <figure anchor="tl-cost-given-periods" 
       title="Periodic Link Cost with C0' in Given Periods">
          <artwork align="center"><![CDATA[  Link Cost 
    ^
    |                                              C1 = Infinity
    |    C1__ ...        C1___________     C1___________
    |
    |                                                  
    |             C0'______         C0'______  
  C0|______ ...                                         C0______                  
    |
   -+----------------------------------------------------------->Time
    |T0              T0'   T1'         T2'   T3'         T4     T5
    |                | 400s |<-5,300s->| 400s |<-5,300s->| 400s |  
    |                |<--95m(5,700s)-->|<--95m(5,700s)-->|]]>
</artwork>
      </figure>
 </t>
    </section>
<!-- "Change In Given Periods" -->


    <section title="Change in Given Interval">
     <t>The cost of a temporal link is
C0 for a time interval in every time period except for a given time interval. 
In the given interval, the cost of the link is
Ca, for example, Ca = 3*C0.</t>

     <t>When the given interval is 5,000 seconds from given time T0' 
as shown in <xref target = "tl-cost-given-interval"/>, 
the cost of the link is Ca from T2
for (T1' - T2) seconds, C0 from T1' for (T3 - T1') seconds, and then
Infinity for the rest of the period (95 minutes from T2 to T4). 
 
For the time period from T0' to T2, which overlaps with the
time period from T1 to T2,
the cost of the link is Infinity, which is the bigger cost
(Infinity > Ca)
in the overlapped period (i.e., from T0' to T2).

For the time period from T2 to T1', which overlaps with the
time period from T2 to T3,
the cost of the link is Ca, which is the bigger cost (Ca > C0)
in the overlapped period (i.e., from T2 to T1').

      <figure anchor="tl-cost-given-interval" 
       title="Periodic Link Cost with Ca in Given Interval">
          <artwork align="center"><![CDATA[Link Cost 
  ^
  |                                              C1 = Infinity
  |    C1___________        C1___________     C1___________
  |
  |                 Ca____                                                
  |                       
C0|______                 ____C0        C0______                  
  |            |<-5,000s->|
 -+--------------------------------------------------------->Time
  |T0    T1    T0'    T2 T1' T3           T4     T5
  | 400s |            | 400s |            | 400s |          |
  |<-- 95m(5,700s) -->|<-- 95m(5,700s) -->|<--95m(5,700s)-->|]]>
</artwork>
      </figure>
 </t>
    </section>
<!-- "Change In Given Intervals" -->

  </section> 
<!-- "Temporal Link Cost Functions" -->


  <section anchor="extension" title="Extensions to IGP">
    <t>This section defines cost function Sub-TLVs for
representing a cost function of a temporal link and 
describes procedures for handling temporal links.</t>

  <section anchor="sub-tlvs" title="Cost Function Sub-TLVs">
    <t>Three link cost function Sub-TLVs are defined. 
They are Recurrent time interval Sub-TLV,
Limited Recurrent time interval Sub-TLV and 
Fixed time interval Sub-TLV.</t>

    <t>Recurrent time interval Sub-TLV is shown in 
<xref target = "re-interval"/>. 
Its value contains Start-time, Interval-length and Period.

This Sub-TLV with Start-time = T0, Interval-length = 400 
and Period = 5,700
represents a cost function similar to the one as 
shown in <xref target = "tl-cost-periodic"/>. 
The cost of the link is normal link cost such as C0 from a time 
indicated by Start-time = T0 for a time interval indicated 
by Interval-length = 400 seconds in every period indicated 
by Period = 5,700 seconds, 
and Infinity for the rest of time in every period. 

      <figure anchor="re-interval" 
       title="Recurrent Time Interval Sub-TLV">
          <artwork align="center"><![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   
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|         Type (TBD1)           |              Length           |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Start-time                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         Interval-length                       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            Period                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]>
          </artwork>
      </figure>
</t>

<t>Limited Recurrent time interval Sub-TLV is shown in 
<xref target = "l-re-interval"/>. 
Its value contains Start-time, Interval-length, Period, 
Number-periods, and Cost.

This Sub-TLV with Start-time = T0', Interval-length = 400, 
Period = 5,700, Number-periods = 2 and Cost = C0'
represents a part of a cost function similar to
the one as shown in 
<xref target = "tl-cost-given-periods"/>. 

The cost of the link is Cost = C0' 
from a time indicated by Start-time = T0' 
for a time interval indicated by Interval-length = 400 seconds 
in each period indicated by Period = 5,700 seconds 
for the number of periods indicated by Number-periods = 2 periods, 
and Infinity for the rest of time in each of these 2 periods. 
</t>

    <t>This Sub-TLV with Start-time = T0', Interval-length = 400, 
Period = 5,700, Number-periods = 2 and Cost = C0' and 
Recurrent time interval Sub-TLV 
with Start-time = T0, Interval-length = 400 and Period = 5,700
represent a cost function similar to
the one as shown in 
<xref target = "tl-cost-given-periods"/>.

      <figure anchor="l-re-interval" 
       title="Limited Recurrent Time Interval Sub-TLV">
          <artwork align="center"><![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   
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|           Type (TBD2)         |             Length            |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Start-time                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Interval-length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            Period                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Number-periods        |             Cost              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]>
          </artwork>
      </figure>
</t>

<t>Fixed time interval Sub-TLV is shown in 
<xref target = "fix-interval"/>.
Its value contains Start-time, Interval-length and Cost.
This Sub-TLV with Start-time = T0', Interval-length = 5,000 
and Cost = Ca
represents a part of a cost function similar to 
the one as shown in 
<xref target = "tl-cost-given-interval"/>. 

The cost of the link is Cost = Ca 
from a time indicated by Start-time = T0' 
for a time interval indicated by Interval-length = 5,000 seconds.
</t>

<t>This Sub-TLV with Start-time = T0', Interval-length = 5,000 
and Cost = Ca and  
Recurrent time interval Sub-TLV 
with Start-time = T0, Interval-length = 400 and Period = 5,700
represent a cost function similar to
the one as shown in 
<xref target = "tl-cost-given-interval"/>.

      <figure anchor="fix-interval" 
       title="Fixed Time Interval Sub-TLV">
          <artwork align="center"><![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   
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    
|          Type (TBD3)          |         Length                |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Start-time                          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         Interval-length                       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Cost                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]>
          </artwork>
      </figure>
</t>


<t>Every node distributes a cost function configured 
on each temporal link of the node to the other nodes in the network. 

For OSPFv2, the cost function Sub-TLVs for a cost function 
configured on a temporal link of the node 
is distributed in the OSPFv2 Extended Link TLV for the link 
in the OSPFv2 Extended Link Opaque LSA with LS Type 10 defined in 
<xref target = "RFC7684"/>. 
</t>

<t>For OSPFv3, the cost function Sub-TLVs for a cost function 
configured on a temporal link of the node 
is distributed in the Router-Link TLV for the link in the OSPFv3 
E-Link-LSA defined in 
<xref target = "RFC8362"/>.
</t>

<t>For IS-IS, 
the cost function Sub-TLVs for a cost function configured 
on a temporal link of the node is included in 
the Extended IS Reachability TLV of TLV type 22 
for the link in a Link State Protocol data unit (PDU) (LSP).
</t>
  </section> 
<!-- "Cost Function Sub-TLVs" -->


  <section anchor="proc" title="Procedures">
   <t>Every node in a network maintains status of each 
of temporal links in its link state database (LSDB). 
The status includes cost function such as cost function Sub-TLVs 
for the link, the down or up state of the link. 
Every node also maintains the earliest link change time (ELCT) 
at which the cost of a temporal link will change from C 
(which is not Infinity) to Infinity or vice versa. </t>

<t>
Every node computes the shortest paths using the costs of links 
at ELCT before ELCT and builds a next routing/forwarding table (NRT) 
based on the paths. 
When the time is ELCT, every node uses its NRT as its current 
routing/forwarding table, and then every node finds a new ELCT, 
computes the shortest paths using the costs of links at the new ELCT 
before the new ELCT and builds a new next routing/forwarding table (NRT) 
based on the paths.
Note that the clocks on all the nodes in a network must be synchronized. 
</t>

  </section> 
<!-- "Procedures" -->
  </section> 
<!-- "Extensions to IGP" -->


  <section anchor="Security" title="Security Considerations">
   <t>TBD.</t>
  </section>
  <section anchor="IANA" title="IANA Considerations">
<t>TBD.
</t>
  </section>


 </middle>
 <back>
  <references title="Normative References">
        <reference anchor="ISO10589" quoteTitle="true" derivedAnchor="ISO10589">
          <front>
            <title>Information technology -- Telecommunications and information exchange between systems -- Intermediate System to Intermediate System intra-domain routing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)</title>
            <seriesInfo name="ISO/IEC" value="10589:2002, Second Edition"/>
            <author>
              <organization abbrev="ISO" showOnFrontPage="true">International Organization for Standardization</organization>
            </author>
            <date month="November" year="2002"/>
          </front>
        </reference>
   <?rfc include="reference.RFC.2119"?>
   <?rfc include="reference.RFC.8174"?>
   <?rfc include="reference.RFC.5305"?>
   <?rfc include="reference.RFC.7684"?>
   <?rfc include="reference.RFC.8362"?>

  </references>
  <references title="Informative References">
   <?rfc include="reference.RFC.7356"?>

  </references>

    <section numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t>The authors would like to thank Bruno Decraene, and Donald E. Eastlake
         for the valuable comments and suggestions on this draft.</t>
    </section>


<!--
    <section numbered="false" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-contributors">Contributors</name>

      <t>The following people have substantially contributed to this document:<figure
          align="left">
          <artwork><![CDATA[
Donald E. Eastlake 3rd
Futurewei
Phone: +1-508-333-2270
Email: d3e3e3@gmail.com
]]></artwork>
        </figure></t>
    </section>
-->


 </back>
</rfc>
