[mpls] Some comments on draft-yasukawa-mpls-p2mp-oam-reqs-00.txt

dimitri papadimitriou <dpapadimitriou@psg.com> Sat, 20 August 2005 11:05 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6R9s-00054y-5k; Sat, 20 Aug 2005 07:05:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E6R9q-00054Y-8N for mpls@megatron.ietf.org; Sat, 20 Aug 2005 07:05:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15462 for <mpls@ietf.org>; Sat, 20 Aug 2005 07:04:59 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E6Rjy-0001VQ-BT for mpls@ietf.org; Sat, 20 Aug 2005 07:42:23 -0400
Received: from localhost ([127.0.0.1]) by psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1E6R9m-000Gae-Qs for mpls@ietf.org; Sat, 20 Aug 2005 11:04:59 +0000
Message-ID: <43070E48.5010902@psg.com>
Date: Sat, 20 Aug 2005 13:04:40 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mpls@ietf.org
Content-Type: multipart/mixed; boundary="------------080709020001040502080400"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b148ead9c6581b10314b24a9438d3a5f
Cc:
Subject: [mpls] Some comments on draft-yasukawa-mpls-p2mp-oam-reqs-00.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel.be
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

looking at this doc some comments

in section 4.2 "These functions should allow an operator to stipulate 
the maximum amount of time to wait until responses are heard from all 
points along the path, as well a cut-offs for the number of paths tested."

-> not sure to understand what "all points" means in this context, also 
if you don't receive an answer what are you going to do (is not btw a 
situation which is susceptible to occur ?)

in section 4.3 " Note that path characterization should lead to the 
operator being able to deduce the full tree for a P2MP LSP. To achieve 
this, it is important that the branching points on that tree are clearly
identified."

-> does this sentence means that a mechanism should be made available to 
poll for specific branching point liveliness ?

in section 4.6 "As described in [MPLS-OAM], network elements MUST 
provide alarm suppression and aggregation to prevent the generation of 
superfluous alarms within or across network layers."

-> would it be possible to be a bit more specific in the P2MP context 
what does aggregation of alarms means ? (and which alarms ?) to which 
"network layers" is this sentence referring to ? in general, i find this 
section difficult to parse

in section 4.8 "As described in [MPLS-OAM], these procedures
will detect a broad range of defects, and SHOULD be operable where
Since MPLS P2MP LSPs span multiple routing areas, or multiple Service 
Provider domains."

-> would it be possible to clarify the beginning of the sentence refers 
to failure detection, the last part about multi-area/multi-AS ?

in section 4.11 "Fundamental to understanding traffic flows within a 
network that supports P2MP LSPs will be the knowledge of where the 
branch points exist within the network."

-> do you assume that the tree decomposition is unique ? it seems to me 
you need to also have the branch point relationship - clarifying what 
the term "where" means would help here
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls