draft-ietf-mpls-crldp-unnum-04.txt   draft-ietf-mpls-crldp-unnum-05.txt 
Network Working Group Kireeti Kompella Network Working Group Kireeti Kompella
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: August 2002 Yakov Rekhter Expiration Date: September 2002 Yakov Rekhter
Juniper Networks Juniper Networks
Alan Kullberg Alan Kullberg
NetPlane Systems NetPlane Systems
Signalling Unnumbered Links in CR-LDP Signalling Unnumbered Links in CR-LDP
draft-ietf-mpls-crldp-unnum-04.txt draft-ietf-mpls-crldp-unnum-05.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 4, line 27 skipping to change at page 4, line 27
6. Signalling Unnumbered Links in EROs 6. Signalling Unnumbered Links in EROs
A new subobject of the Explicit Route Object (ERO) is used to specify A new subobject of the Explicit Route Object (ERO) is used to specify
unnumbered links. This subobject has the following format: unnumbered links. This subobject has the following format:
Figure 2: Unnumbered Interface ID Subobject Figure 2: Unnumbered Interface ID Subobject
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| Type | Length | |0|0| Type = 0x0805 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID (32 bits) | | Interface ID (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Type is 0x0805 (Unnumbered Interface ID) and the Length is 8. The Type is 0x0805 (Unnumbered Interface ID) and the Length is 12.
The L bit is set to indicate a loose hop, and cleared to indicate a
strict hop.
The Interface ID is the identifier assigned to the link by the LSR The Interface ID is the identifier assigned to the link by the LSR
specified by the router ID. specified by the router ID.
6.1. Processing the IF_ID TLV 6.1. Processing the IF_ID TLV
When an LSR receives a REQUEST message containing the IF_ID TLV (see When an LSR receives a REQUEST message containing the IF_ID TLV (see
[GMPLS-CRLDP]) with the IF_INDEX TLV, the LSR processes this TLV as [GMPLS-CRLDP]) with the IF_INDEX TLV, the LSR processes this TLV as
follows. The LSR must have information about the identifiers assigned follows. The LSR must have information about the identifiers assigned
by its neighbors to the unnumbered links between the neighbors and by its neighbors to the unnumbered links between the neighbors and
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/