<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.ali-ccamp-rsvp-node-id-based-hello'>
<front>
<title>Node ID based RSVP Hello: A Clarification Statement</title>

<author initials='R' surname='Rahman' fullname='Reshad Rahman'>
    <organization />
</author>

<author initials='D' surname='Prairie' fullname='Danny  Prairie'>
    <organization />
</author>

<author initials='D' surname='Papadimitriou' fullname='Dimitri Papadimitriou'>
    <organization />
</author>

<author initials='Z' surname='Ali' fullname='Zafar Ali'>
    <organization />
</author>

<date month='April' day='16' year='2004' />

<abstract><t>Use of node-id based RSVP Hello messages is implied in a number of cases, e.g., when data and control plan are separated, when TE links are unnumbered. Furthermore, when link level failure detection is performed by some means other than RSVP Hellos, use of node-id based Hellos is optimal for detecting signaling adjacency failure for RSVP- TE. Nonetheless, this implied behavior is unclear and this document formalizes use of node-id based RSVP Hello sessions as a best current practice (BCP) in some scenarios.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-ali-ccamp-rsvp-node-id-based-hello-01' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-ali-ccamp-rsvp-node-id-based-hello-01.txt' />
</reference>

