draft-ietf-ospf-te-node-addr-06.txt   draft-ietf-ospf-te-node-addr-07.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: November 2009 Expiration Date: June 2010
K. Kompella K. Kompella
Juniper Networks Juniper Networks
May 04, 2009 December 02, 2009
Advertising a Router's Local Addresses in OSPF TE Extensions Advertising a Router's Local Addresses in OSPF TE Extensions
draft-ietf-ospf-te-node-addr-06.txt draft-ietf-ospf-te-node-addr-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 4, line 24 skipping to change at page 4, line 24
advertising router's other local addresses, i.e., loopback and non-TE advertising router's other local addresses, i.e., loopback and non-TE
interface addresses. OSPFv2 stub links in the router LSA [RFC2328], interface addresses. OSPFv2 stub links in the router LSA [RFC2328],
provide stub reachability information to the router but are not provide stub reachability information to the router but are not
sufficient to learn all the local addresses of a router. In sufficient to learn all the local addresses of a router. In
particular for a subnetted point-to-point (P2P) interface the stub particular for a subnetted point-to-point (P2P) interface the stub
link ID is the subnet address. While for a non-subnetted interface link ID is the subnet address. While for a non-subnetted interface
the stub link ID is the neighbor address. Intra-prefix LSAs in the stub link ID is the neighbor address. Intra-prefix LSAs in
OSPFv3 [RFC5340] are also not sufficient to learn the local OSPFv3 [RFC5340] are also not sufficient to learn the local
addresses. addresses.
For the above reasons this document proposes an enhancement to OSPF For the above reasons this document defines an enhancement to OSPF TE
TE extensions to advertise the local addresses of a node. extensions to advertise the local addresses of a node.
3. Rejected Potential Solution 3. Rejected Potential Solution
A potential solution would be to advertise a TE link TLV for each A potential solution would be to advertise a TE link TLV for each
local address, possibly with a new link type. However, this is local address, possibly with a new link type. However, this is
inefficient since the only meaningful information is the address. inefficient since the only meaningful information is the address.
Furthermore, this would require implementations to process these TE Furthermore, this would require implementations to process these TE
link TLVs differently from others; for example, the TE metric is link TLVs differently from others; for example, the TE metric is
normally considered a mandatory sub-TLV, but would have no meaning normally considered a mandatory sub-TLV, but would have no meaning
for a local address. for a local address.
skipping to change at page 5, line 39 skipping to change at page 5, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Prefix n | | IPv4 Prefix n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Each local IPv4 address is encoded as a <Prefix Length, Prefix> Each local IPv4 address is encoded as a <Prefix Length, Prefix>
tuple. Prefix Length is encoded in 1 byte. It is the number of bits tuple. Prefix Length is encoded in 1 byte. It is the number of bits
in the Address and can be at most 32. Prefix is an IPv4 address in the Address and can be at most 32. Prefix is an IPv4 address
prefix and is encoded in 4 bytes with zero bits as necessary. prefix and is encoded in 4 bytes with zero bits as necessary.
The Node IPv4 Local Address sub-TLV length is in octets. It is the The Node IPv4 Local Address sub-TLV length is in octets. It is the
sum of all n IPv4 Address encodings in the sub-TLV where n is the sum of the lengths of all n IPv4 Address encodings in the sub-TLV
number of local addresses included in the sub-TLV. where n is the number of local addresses included in the sub-TLV.
The node IPv6 local address sub-TLV has a type of 2 and contains one The node IPv6 local address sub-TLV has a type of 2 and contains one
or more local IPv6 addresses. It has the following format: or more local IPv6 addresses. It has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | Length | | 2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Len 1 | Prefix 1 Opt. | IPv6 Prefix 1 | | Prefix Len 1 | Prefix 1 Opt. | IPv6 Prefix 1 |
skipping to change at page 6, line 26 skipping to change at page 6, line 26
Each IPv6 address MUST be represented by a combination of three Each IPv6 address MUST be represented by a combination of three
fields: PrefixLength, PrefixOptions, and Address Prefix. PrefixLength fields: PrefixLength, PrefixOptions, and Address Prefix. PrefixLength
is the length in bits of the prefix and is an 8 bit field. is the length in bits of the prefix and is an 8 bit field.
PrefixOptions is an 8-bit field describing various capabilities PrefixOptions is an 8-bit field describing various capabilities
associated with the prefix [RFC5340]. Address Prefix is an encoding associated with the prefix [RFC5340]. Address Prefix is an encoding
of the prefix itself as an even multiple of 32-bit words, padding of the prefix itself as an even multiple of 32-bit words, padding
with zero bits as necessary. This encoding consumes (PrefixLength + with zero bits as necessary. This encoding consumes (PrefixLength +
31) / 32) 32-bit words. 31) / 32) 32-bit words.
The Node IPv6 Local Address sub-TLV length is in octets. It is the The Node IPv6 Local Address sub-TLV length is in octets. It is the
sum of all n IPv6 Address encodings in the sub-TLV where n is the sum of the lengths of all n IPv6 Address encodings in the sub-TLV
number of local addresses included in the sub-TLV. where n is the number of local addresses included in the sub-TLV.
4.2. Operation 4.2. Operation
A router announces one or more local addresses in the node attribute A router announces one or more local addresses in the node attribute
TLV. The local addresses that can be learned from TE LSAs i.e., TLV. The local addresses that can be learned from TE LSAs i.e.,
router address and TE interface addresses SHOULD NOT be advertised in router address and TE interface addresses SHOULD NOT be advertised in
the node local address sub-TLV. The local addresses advertised will the node local address sub-TLV. The local addresses advertised will
depend on the local configuration of the advertising router. The depend on the local configuration of the advertising router. The
default behavior MAY be to advertise all the loopback interface default behavior MAY be to advertise all the loopback interface
addresses. addresses.
The node attribute TLV must appear in exactly one TE LSA originated The node attribute TLV MUST NOT appear in more than one TE LSA
by a router. Furthermore, only one node attribute TLV must be originated by a router. Furthermore, such a LSA MUST NOT include more
advertised in such a LSA. A node attribute TLV must carry at most one than one node attribute TLV. A node attribute TLV MUST NOT carry more
Node IPv4 Local Address sub-TLV and at most one Node IPv6 Local than one Node IPv4 Local Address sub-TLV. A node attribute TLV MUST
Address sub-TLV. NOT carry more than one Node IPv6 Local Address sub-TLV.
5. Security Considerations 5. Security Considerations
This document does not introduce any further security issues other This document does not introduce any further security issues other
than those discussed in [RFC3630, RFC5329]. than those discussed in [RFC3630, RFC5329].
6. IANA Considerations 6. IANA Considerations
The Node Attribute TLV type has to be IANA assigned from the range 3 The Node Attribute TLV type has to be IANA assigned from the range 3
- 32767 as specified in [RFC3630], from the top level types in TE - 32767 as specified in [RFC3630], from the top level types in TE
 End of changes. 7 change blocks. 
14 lines changed or deleted 14 lines changed or added

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