--- 1/draft-ietf-mpls-crldp-unnum-03.txt	2006-02-05 00:37:45.000000000 +0100
+++ 2/draft-ietf-mpls-crldp-unnum-04.txt	2006-02-05 00:37:45.000000000 +0100
@@ -1,21 +1,21 @@
 
 Network Working Group                             Kireeti Kompella
 Internet Draft                                    Juniper Networks
-Expiration Date: June 2002                           Yakov Rekhter
+Expiration Date: August 2002                         Yakov Rekhter
                                                   Juniper Networks
                                                      Alan Kullberg
                                                   NetPlane Systems
 
                  Signalling Unnumbered Links in CR-LDP
 
-                   draft-ietf-mpls-crldp-unnum-03.txt
+                   draft-ietf-mpls-crldp-unnum-04.txt
 
 1. Status of this Memo
 
    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.
@@ -157,29 +157,29 @@
    |                     Interface ID (32 bits)                    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
    The Type is 0x0805 (Unnumbered Interface ID) and the Length is 8.
 
    The Interface ID is the identifier assigned to the link by the LSR
    specified by the router ID.
 
 6.1. Processing the IF_ID TLV
 
-   When an LSR receives a REQUEST message containing the IF_ID TLV with
-   the IF_INDEX TLV, the LSR processes this TLV as follows.  The LSR
-   must have information about the identifiers assigned by its neighbors
-   to the unnumbered links between the neighbors and the LSR. The LSR
-   uses this information to find a link with tuple <Router ID, local
-   identifier> matching the tuple <IP Address, Interface ID> carried in
-   the IF_INDEX TLV. If the matching tuple is found, the match
-   identifies the link for which the LSR has to perform label
-   allocation.
+   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
+   follows. The LSR must have information about the identifiers assigned
+   by its neighbors to the unnumbered links between the neighbors and
+   the LSR. The LSR uses this information to find a link with tuple
+   <Router ID, local identifier> matching the tuple <IP Address,
+   Interface ID> carried in the IF_INDEX TLV. If the matching tuple is
+   found, the match identifies the link for which the LSR has to perform
+   label allocation.
 
    Otherwise, the LSR SHOULD return an error.
 
 6.2. Processing the ERO object
 
    The Unnumbered Interface ID subobject is defined to be a part of a
    particular abstract node if that node has the Router ID that is equal
    to the Router ID field in the subobject, and if the node has an
    (unnumbered) link or an (unnumbered) Forwarding Adjacency whose local
    identifier (from that node's point of view) is equal to the value