draft-ietf-ccamp-rsvp-node-id-based-hello-00.txt
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 28 July 2004 00:19 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23145 for <ccamp-archive@ietf.org>; Tue, 27 Jul 2004 20:19:04 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpcBV-0002k6-35 for ccamp-archive@ietf.org; Tue, 27 Jul 2004 20:20:51 -0400
Received: from majordom by psg.com with local (Exim 4.41 (FreeBSD)) id 1BpbvN-0005Vt-Q7 for ccamp-data@psg.com; Wed, 28 Jul 2004 00:04:01 +0000
Received: from [80.168.70.142] (helo=relay2.mail.uk.clara.net) by psg.com with esmtp (Exim 4.41 (FreeBSD)) id 1BpbvE-0005QZ-Ip; Wed, 28 Jul 2004 00:03:52 +0000
Received: from du-069-0111.access.clara.net ([217.158.132.111] helo=Puppy) by relay2.mail.uk.clara.net with smtp (Exim 4.34) id 1BpbvB-0005aX-Ap; Wed, 28 Jul 2004 01:03:50 +0100
Message-ID: <001701c47436$5d128f90$6f849ed9@Puppy>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
From: Adrian Farrel <adrian@olddog.co.uk>
To: Zafar Ali <zali@cisco.com>, Dimitri Papadimitriou <Dimitri.Papadimitriou@alcatel.be>, Dimitri Papadimitriou <dpapadimitriou@psg.com>, 'Danny Prairie' <dprairie@cisco.com>, Reshad Rahman <rrahman@cisco.com>
Cc: ccamp@ops.ietf.org
Subject: draft-ietf-ccamp-rsvp-node-id-based-hello-00.txt
Date: Tue, 27 Jul 2004 20:20:48 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RCVD_IN_SORBS autolearn=no version=2.63
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Hi, Just a couple of comments. Cheers, Adrian 2. Introduction Even in the case of packet MPLS, when link failure detection is performed by some means other than RSVP Hellos (e.g., [BFD]), the use of node-id based Hellos is also optimal for detection of signaling adjacency failures for RSVP-TE. This optimally only applies when there is more than one link between a pair of node, right? Say so? Ditto section 3. 2. Introduction This document also clarifies the use of node-id based Hellos when all or a sub-set of TE links are unnumbered. This draft also clarifies use of node-id based Hellos in these scenarios. Repeated? 3. Node-id based RSVP Hellos When a node receives a Hello packet where the destination IP address is its local node-id as advertised in the IGP-TE topology, the node MUST use its node-id in replying to the Hello message. This is an interesting use of MUST when the receiving node knows that the use of node-id is inappropriate. I think it is really cute that Danny and Reshad have decided to swap email addresses :-)
- draft-ietf-ccamp-rsvp-node-id-based-hello-00.txt Adrian Farrel
- Re: draft-ietf-ccamp-rsvp-node-id-based-hello-00.… dimitri papadimitriou