One document matched: draft-dhody-pce-bn-discovery-ospf-07.xml
<?xml version="1.0" encoding="us-ascii"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[]>
<?rfc toc="yes" ?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="4"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="no"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc compact="yes" ?>
<?rfc iprnotified="Yes" ?>
<?rfc strict="no" ?>
<rfc ipr="trust200902" category="std" docName="draft-dhody-pce-bn-discovery-ospf-07" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="OSPF BND">OSPF Protocol Extensions for Boundary Node Discovery (BND)</title>
<author initials="D" surname="Dhody" fullname="Dhruv Dhody">
<organization>Huawei Technologies India Pvt Ltd</organization>
<address>
<postal>
<street>Leela Palace</street>
<city>Bangalore</city>
<region>Karnataka</region>
<code>560008</code>
<country>INDIA</country>
</postal>
<email>dhruv.ietf@gmail.com</email>
</address>
</author>
<author initials="U" surname="Palle" fullname="Udayasree Palle">
<organization>Huawei Technologies India Pvt Ltd</organization>
<address>
<postal>
<street>Leela Palace</street>
<city>Bangalore</city>
<region>Karnataka</region>
<code>560008</code>
<country>INDIA</country>
</postal>
<email>udayasree.palle@huawei.com</email>
</address>
</author>
<date month="August" year="2013" />
<area>Routing</area>
<workgroup>PCE Working Group</workgroup>
<abstract>
<t>The Path Computation Element (PCE) may be used for computing multi-domain (Area or AS) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) Label Switch Path (LSP).</t>
<t>In this circumstance, it is highly desirable to be able to dynamically and automatically discover a set of Boundary Nodes (BN) along with their domain information in a simple way. For that purpose, this document defines extensions to the Open Shortest Path First (OSPF) routing protocol for the advertisement of Boundary Node (BN) Discovery information within an OSPF area or within the entire OSPF routing domain.</t>
</abstract>
</front>
<middle>
<section title="Introduction" toc="default">
<t>This document defines extensions to OSPFv2 <xref target="RFC2328"/> and OSPFv3 <xref target="RFC5340"/> to allow a boundary node in an OSPF routing domain to advertise its location, along with domain information.</t>
<t>Generic capability advertisement mechanisms for OSPF are defined in <xref target="RFC4970"/>. These allow a router to advertise its capabilities within an OSPF area or an entire OSPF routing domain. This document leverages this generic capability advertisement mechanism to fully satisfy the dynamic BN discovery.</t>
<t>This document defines a new TLV (named the Boundary Node Discovery TLV (BND TLV)) to be carried within the OSPF Router Information LSA (<xref target="RFC4970"/>).</t>
<t>The Boundary Node information advertised is detailed in <xref target="SEC_OVERVIEW"/>. Protocol extensions and procedures are defined in <xref target="SEC_BND"/> and <xref target="SEC_PROC"/>.</t>
<t>A detailed description about the need for auto discovery of Boundary Nodes (BN) and thier domains is also provided in this document.</t>
<t>The OSPF extensions defined in this document allow for Boundary Node discovery within an OSPF routing domain. Boundary Node can be an Area Border Router (ABR) or Autonomous System Border Router (ASBR). </t>
<section title="Requirements Language" toc="default">
<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"/>.</t>
</section>
</section>
<section title="Terminology" toc="default">
<t>The following terminology is used in this document.</t>
<t>
<list style="hanging">
<t hangText="ABR:">OSPF Area Border Router. Routers used to connect two IGP areas.</t>
<t hangText="AS:">Autonomous System.</t>
<t hangText="ASBR:">Autonomous System Border Router. Router used to connect together ASes of the same or different service providers via one or more inter-AS links</t>
<t hangText="BN:">A boundary node is either an ABR in the context of inter-area Traffic Engineering or an ASBR in the context of inter-AS Traffic Engineering.</t>
<t hangText="BND:">Boundary Node Discovery</t>
<t hangText="BRPC:">Backward Recursive Path Computation</t>
<t hangText="Domain:">Any collection of network elements within a common sphere of address management or path computational responsibility. Examples of domains include Interior Gateway Protocol (IGP) areas and Autonomous Systems (ASs).</t>
<t hangText="H-PCE:">Hierarchical PCE.</t>
<t hangText="IGP:">Interior Gateway Protocol. Either of the two routing protocols, Open Shortest Path First (OSPF) or Intermediate System to Intermediate System (IS-IS).</t>
<t hangText="LSA:">Link State Advertisement.</t>
<t hangText="OSPF:">Open Shortest Path First.</t>
<t hangText="PCE:">Path Computation Element. An entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints.</t>
<t hangText="TLV:">Type-Length-Variable data encoding.</t>
</list>
</t>
</section>
<section title="Applications" toc="default">
<t>Backward Recursive Path Computation (BRPC) procedure as defined in <xref target="RFC5441"/>, requires Path Computation Element (PCE) <xref target="RFC4655"/> to be aware of the Boundary Nodes (BN) for the inter-domain path computation. This information would be either statically configured at PCE or learned via some mechanism, as listed in <xref target="SEC_OTHER"/>. </t>
<t>In case of static configuration, as shown in the <xref target="fig1"/>, incase of OSPF Area0, configuration of BNs at PCE5 is extensive. BRPC procedure guarantees a best path only if BNs are selected correctly, any change in BNs at run time may lead to sub-optimal path. Also Administrator need to configure ABR / ASBR ID in such a way that it is reachable from all the domains, BND TLV can take care of this automatically.</t>
<t>
<figure title="OSPF Area Topology" suppress-title="false" anchor="fig1" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ +--------------------+
| +-----+|
| Area 2 | PCE2||
| +-----+|
| |
| |
| BN4+----+ |
+--------+----+------+
+----------+----+---------+
| +----+ |
| |
| |
| |
+---------------+ | |+----------------+
| BN1 | | || BN5 |
| +-+-++ +++--+ |
| | | || ||| | |
| +-+-++ +++--+ |
| | | || |
| BN2 | | || BN6 |
| +-+-++ Area 0 +++--+ |
| Area 1 | | || ||| | Area 3 |
| +-+-++ +++--+ |
| | | || |
| BN3 | | +-----+ || BN7 |
|+-----+ +-+-++ | PCE5| +++--+ +-----+ |
|| PCE1| | | || +-----+ ||| | | PCE3| |
|+-----+ +-+-++ +++--+ +-----+ |
| | | || |
+---------------+ | |+----------------+
| |
| |
| +----+ |
+----------+----+---------+
+--------+----+------+
| BN8 +----+ |
| |
| |
| Area 4 +-----+|
| | PCE4||
| +-----+|
+--------------------+
]]></artwork>
</figure>
</t>
<t>The problems with existing mechanism to discover Boundary nodes are listed in <xref target="SEC_OTHER"/>.</t>
<t>Hierarchal PCE (H-PCE) <xref target="RFC6805"/> mechanim MAY require a parent PCE to be aware of child domain's boundary node, child PCE in any case should be aware of all its boundary nodes and can use mechnims as described in this document.</t>
</section>
<section title="Existing Mechanisms " toc="default" anchor="SEC_OTHER">
<section title="OSPF LSA " toc="default">
<t>
<list style="symbols">
<t>E bit and B bit of Router LSA defined in <xref target="RFC2328"/> can help in finding a router acting as ABR/ASBR but there is no way to find out the domain information of this ABR/ASBR. As stated in <xref target="SEC_DOMAIN"/>, Selection of correct BN is based on domain and thus it is ineffective.</t>
<t>Selection of ABR based on summary LSA or ASBR based on AS-external LSA is not a good idea, first it requires PCE to look into the OSPF core data structure - Link State Database (LSDB) thus adding to coupling, second it MAY require Border Gateway Protocol (BGP) routes to be redistributed into OSPF which is also not a good network design principle. </t>
</list>
</t>
</section>
<section title="Inter-AS TE Link" toc="default">
<t>
<list style="symbols">
<t><xref target="RFC5392"/> specifies how to advertise TE properties of inter-AS links; through which ASBR and remote AS can be discovered, but ABR and their domain information cannot be discovered via above RFC.</t>
<t>AS is made up of multiple Area, there maybe a need to clearly identify a BN by combination of both AS number and Area-id. Refer <xref target="DOMAIN-SEQ"/>. </t>
<t>AS shown in below figure, just the knowledge of AS 100 and AS 200 is not sufficient, the BN should have both AS and Area information. The area information cannot be provided by <xref target="RFC5392"/>.</t>
</list>
</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ |
| +-------------+ +----------------+
| |Area 2 | |Area 4 |
| | +--+| | +--+ |
| | | || | | | |
| | +--+ +--+| | +--+ +--+ |
| | | | | | | | |
| | *--+ | | +--+ |
| | / +--+ | | +--+ |
| |/ | | | | | | |
| / +--+ | | +--+ +--+ |
| /| +--+ |+--------------+| | | |
|/ | | | ++-+ +-++ +--+ |
+-------------+/ | +--+ || | | || |
| /| | ++-+ +-++ |
| +--*|| +-------------+| |+----------------+
| | ||| | +--+ |
| +--+|| | | | |
| +--+ || | +--+ |
| | | || | |
| +--+ || | |
| || | +--+ |
|+--+ || | | | |
|| | || | +--+ |
|+--+ || | |
| || | +--+ |
| +--+ || +------------+ | | | |+----------------+
| | | || |Area 3 +-++ +--+ +-++ Area 5 |
| +--+ || | | || | || |
| || | +-++ +-++ |
| +--+|| | +--+ | | Area 0 || +--+ |
| | ||| | | | | +--------------+| | | |
| +--*|| | +--+ | | +--+ |
| \| | | | +--+ |
|Area 1 |\ | +--+ | | +--+ | | |
+-------------+|\ | | | | | | | +--+ |
| \| +--+ +--+ | +--+ |
| \ | | | |
| |\ +--+ | +--+ |
| | \ +--+ | | | | |
| | \| | | | +--+ |
| | *--+ | | |
| | | | |
| +------------+ +----------------+
|
|
As 100 | AS 200
|]]></artwork>
</figure>
</t>
</section>
<section title="OSPF Area Topology" toc="default">
<t>
<list style="symbols">
<t>Consider OSPF topology as shown in <xref target="fig1"/>, One can make a generalization that all ABR connects to Area 0, and one doesnt need the area information. </t>
<t>But as per <xref target="RFC3509"/>, there are alternative interpretaion of ABR, which needs to be considered. If there is a connectivity between Area 1 and Area 2 directly that needs to be considered. In the scope of path computation. it is not correct to force all paths to go through area 0, irrespective of actual topology.</t>
</list>
</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ . .
. Area 0 .
+--+ +--+
..|R1|.. ..|R2|..
. +--+ .. +--+ .
. .. .
. +--+ .
. Area1 |R3| Area2 .
. +--+ +--+ .
. .. |R4| .
. . . +--+ .
....... .......]]></artwork>
</figure>
</t>
</section>
</section>
<section title="Other Considerations" toc="default" >
<section title="Static Configurations" toc="default" >
<t>A simple solution would be to configure BNs (ABR and ASBR) at PCE(s) along with their domain information. As this information is fairly static this could work in simple situations. But as PCE are being used in bigger and multiple domains, any sort of static configurations would put extra effort on the system administrator. Selection of correct BNs is the core of any inter-domain path computation procedure, this information should be dynamically learned and maintained. </t>
</section>
<section title="Importance of Domain Information along with BNs" toc="default" anchor="SEC_DOMAIN">
<t>There are methods to learn BNs dynamically from IGP, but the knowledge of neighboring-domains is not possible to obtain. Without this the correct BN based on the domain-path can not be selected. <xref target="RFC5441"/> mentions:</t>
<t>"Note that PCE(i) only considers the entry BNs of domain(i), i.e., only the BNs that provide connectivity from domain(i-1). In other words, the set BN-en(k,i) is only made of those BNs that provide connectivity from domain (i-1) to domain(i)."</t>
<t>This selection of correct BNs providing connectivity between correct domains cannot be made by the information obtained from IGP. Without the correct selection we would not be following <xref target="RFC5441"/>. </t>
</section>
<section title="Relationship to Domain-Sequence" toc="default">
<t><xref target="DOMAIN-SEQ"/> provides a standard representation of Domain Sequence in all deployment scenarios. The Domain Information carried in the BN-DOMAIN sub-tlv is same as the sub-objects inside the domain sequence.</t>
</section>
</section>
<section title="Overview" toc="default" anchor="SEC_OVERVIEW">
<section title="Boundary Node (BN) Discovery Information" toc="default">
<t> The BN discovery information is composed of:</t>
<t>
<list style="symbols">
<t>The BN location: an IPv4 and/or IPv6 address that is used to reach the BN. It is RECOMMENDED to use an address that is always reachable from all connected domains;</t>
<t>The set of two or more Domain(s) into which the BN has connectivity;</t>
</list>
</t>
<t>Changes in BN discovery information may occur as a result of BN configuration update or domain status change.
</t>
</section>
<section title="Flooding Scope" toc="default">
<t>The flooding scope for BN information advertised through OSPF can be limited to OSPF area(s) the BN belongs to, or can be extended across the entire OSPF routing domain.</t>
</section>
</section>
<section title="The OSPF BND TLV" toc="default" anchor="SEC_BND">
<t>The OSPF BN Discovery TLV (BND TLV) contains a non-ordered set of sub-TLVs.</t>
<t>The format of the OSPF BND TLV and its sub-TLVs is identical to the TLV format used by the Traffic Engineering Extensions to OSPF <xref target="RFC3630"/>. That is, the TLV is composed of 2 octets for the type, 2 octets specifying the TLV length, and a value field. The Length field defines the length of the value portion in octets.</t>
<t>The OSPF BND TLV has the following format:</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
// sub-TLVs //
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ Type: To be assigned by IANA (suggested value 8)
Length: Variable
Value: This comprises of following sub-TLVs
Two sub-TLVs are defined:
Sub-TLV type Length Name
1 variable BN-ADDRESS sub-TLV
2 4 BN-DOMAIN sub-TLV
]]></artwork>
</figure>
</t>
<t>The BN-ADDRESS and BN-DOMAIN sub-TLVs MUST always be present within the BND TLV.</t>
<t>Malformed BND TLVs or sub-TLVs not explicitly described in this document MUST cause the LSA to be treated as malformed according to the normal procedures of OSPF.</t>
<t>Any unrecognized sub-TLV MUST be silently ignored.</t>
<t>The BND TLV is carried within an OSPF Router Information LSA defined in <xref target="RFC4970"/>.</t>
<t>The following sub-sections describe the sub-TLVs which are carried within the BND TLV.</t>
<section title="BN-ADDRESS Sub-TLV" toc="default">
<t>The BN-ADDRESS sub-TLV specifies an IP address that can be used to reach the BN. It is RECOMMENDED to make use of an address that is always reachable, provided that the BN is alive and reachable.</t>
<t>The BN-ADDRESS sub-TLV is mandatory; it MUST be present within the BND TLV. It MAY appear twice, when the BN has both an IPv4 and IPv6 address. It MUST NOT appear more than once for the same address type. If it appears more than once for the same address type, only the first occurrence is processed and any others MUST be ignored.</t>
<t>The format of the BN-ADDRESS sub-TLV is as follows:</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ 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 = 1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| address-type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
// BN IP Address //
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
BN-ADDRESS sub-TLV format
]]></artwork>
</figure>
</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ Type: 1
Length: 8 (IPv4) or 20 (IPv6)
Address-type:
1 IPv4
2 IPv6]]></artwork>
</figure>
</t>
<t>Reserved: SHOULD be set to zero on transmission and MUST be ignored on receipt.</t>
<t>BN IP Address: The IP address to be used to reach the BN.</t>
</section>
<section title="BN-DOMAIN Sub-TLV" toc="default">
<t>The BN-DOMAIN sub-TLV specifies a BN-Domain (area or AS) where the BN has topology connectivity.</t>
<t>The BN-DOMAIN sub-TLV is mandatory; it MUST be present within the BND TLV.</t>
<t>A BND TLV MUST include two or more BN-DOMAIN sub-TLVs as the BN has connectivity into multiple BN-Domains.</t>
<t>The BN-DOMAIN sub-TLV has the following format:</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ 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 = 2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Domain-type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Domain ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
BN-DOMAIN sub-TLV format
]]></artwork>
</figure>
</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[ Type: 2
Length: 8
Two domain-type values are defined:
1 OSPF Area ID
2 AS Number
]]></artwork>
</figure>
</t>
<t> Domain ID: With the domain-type set to 1, this indicates the 32-bit Area ID of an area where the BN (ABR) has connectivity. With domain-type set to 2, this indicates an AS number of an AS where the BN (ASBR) has connectivity. When the AS number is coded in two octets, the AS Number field MUST have its first two octets set to 0.</t>
</section>
</section>
<section title="Elements of Procedure" toc="default" anchor="SEC_PROC">
<t>The BND TLV is advertised within OSPFv2 Router Information LSAs (Opaque type of 4 and Opaque ID of 0) or OSPFv3 Router Information LSAs (function code of 12), which are defined in <xref target="RFC4970"/>. As such, elements of procedure are inherited from those defined in <xref target="RFC4970"/>.</t>
<t>In OSPFv2, the flooding scope is controlled by the opaque LSA type(as defined in <xref target="RFC5250"/>) and in OSPFv3, by the S1/S2 bits (as defined in <xref target="RFC5340"/>). If the flooding scope is area local, then the BND TLV MUST be carried within an OSPFv2 type 10 router information LSA or an OSPFV3 Router Information LSA with the S1 bit set and the S2 bit clear. If the flooding scope is the entire IGP domain, then the BND TLV MUST be carried within an OSPFv2 type 11 Router Information LSA or OSPFv3 Router Information LSA with the S1 bit clear and the S2 bit set.</t>
<t>When the BN function is deactivated, the OSPF speaker MUST originate a new Router Information LSA that no longer includes the corresponding BND TLV, provided there are other TLVs in the LSA. If there are no other TLVs in the LSA, it MUST either send an empty Router Information LSA or purge it by prematurely aging it.</t>
<t>The BN address (i.e., the address indicated within the BN-ADDRESS sub-TLV) SHOULD be reachable via some prefixes advertised by OSPF.</t>
<t>The BND TLV information regarding a specific BN is only considered current and useable when the router advertising this information is itself reachable via OSPF calculated paths in the same area of the LSA in which the BND TLV appears.</t>
<t>A change in the state of a BN (activate, deactivate, domain change) MUST result in a corresponding change in the BND TLV information advertised by an OSPF router (inserted, removed, updated)in its LSA. The way BNs determine the information they advertise, and how that information is made available to OSPF, is out of the scope of this document. Some information may be configured and other information may be automatically determined by the OSPF.</t>
<t>A change in information in the BND TLV MUST NOT trigger any SPF computation at a receiving router.</t>
</section>
<section title="Backward Compatibility" toc="default">
<t>The BND TLV defined in this document does not introduce any interoperability issues.</t>
<t>A router not supporting the BND TLV will just silently ignore the TLV as specified in <xref target="RFC4970"/>.</t>
</section>
<section title="Impact on Network" toc="default">
<t>The routers acting as BNs will originate Opaque LSA with BND Tlv; As there are only few BNs exist in the network, the performance impact in flooding is very less. </t>
</section>
<section title="IANA Considerations" toc="default">
<section title="OSPF TLV" toc="default">
<t>IANA has defined a registry for TLVs carried in the Router Information LSA defined in <xref target="RFC4970"/>. A number of IANA considerations have been highlighted in previous sections of this document. IANA is requested to make the following allocations.</t>
<t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""><![CDATA[Value TLV Name Reference
----- -------- ----------
To be BND (this document)
assigned
by IANA]]></artwork>
</figure>
</t>
</section>
</section>
<section title="Security Considerations" toc="default">
<t>This document defines OSPF extensions for BN discovery within an administrative domain. Hence the security of the BN discovery relies on the security of OSPF.</t>
<t>Mechanisms defined to ensure authenticity and integrity of OSPF LSAs <xref target="RFC2154"/>, and their TLVs, can be used to secure the BN Discovery information as well.</t>
<t>OSPF provides no encryption mechanism for protecting the privacy of LSAs and, in particular, the privacy of the BN discovery information.</t>
</section>
<section title="Manageability Considerations" toc="default">
<t>TBD</t>
</section>
<section title="Acknowledgments" toc="default">
<t>We would like to thank Quintin Zhao, Daniel King, Adrian Ferral, Suresh babu, Pradeep Shastry, Saravana Kumar, Srinivasan and Venugopal Reddy for their useful comments and suggestions.</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119.xml" ?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.2154.xml" ?>
<?rfc include="reference.RFC.2328.xml" ?>
<?rfc include="reference.RFC.3509.xml" ?>
<?rfc include="reference.RFC.3630.xml" ?>
<?rfc include="reference.RFC.4655.xml" ?>
<?rfc include="reference.RFC.4970.xml" ?>
<?rfc include="reference.RFC.5250.xml" ?>
<?rfc include="reference.RFC.5340.xml" ?>
<?rfc include="reference.RFC.5392.xml" ?>
<?rfc include="reference.RFC.5441.xml" ?>
<?rfc include="reference.RFC.6805.xml" ?>
<!--DOMAIN-SEQ-->
<reference anchor="DOMAIN-SEQ">
<front>
<title>Standard Representation Of Domain Sequence (draft-ietf-pce-pcep-domain-sequence-02)</title>
<author initials="D" surname="Dhody" fullname="Dhruv Dhody">
<organization />
</author>
<author initials="U" surname="Palle" fullname="Udayasree Palle">
<organization />
</author>
<author initials="R" surname="Casellas" fullname="Ramon Casellas">
<organization />
</author>
<date month="Feb" year="2013" />
</front>
</reference>
</references>
</back>
</rfc>| PAFTECH AB 2003-2026 | 2026-04-24 12:24:27 |