RE: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt

neil.2.harrison@bt.com Wed, 06 July 2005 10:40 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dq7KY-0002W9-6I; Wed, 06 Jul 2005 06:40:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dq7KV-0002VV-SI for mpls@megatron.ietf.org; Wed, 06 Jul 2005 06:40:35 -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 GAA22161 for <mpls@ietf.org>; Wed, 6 Jul 2005 06:40:29 -0400 (EDT)
From: neil.2.harrison@bt.com
Received: from smtp4.smtp.bt.com ([217.32.164.151]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dq7e5-0002I5-9Y for mpls@ietf.org; Wed, 06 Jul 2005 07:00:50 -0400
Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Jul 2005 11:32:39 +0100
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Wed, 6 Jul 2005 11:32:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt
Date: Wed, 06 Jul 2005 11:32:35 +0100
Message-ID: <0536FC9B908BEC4597EE721BE6A353890A9F1D77@i2km07-ukbr.domain1.systemhost.net>
Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt
Thread-Index: AcWBtD5uzNGTBNRkS/+OMb6ZlA++ngAXgcgQ
To: yasukawa.seisho@lab.ntt.co.jp
X-OriginalArrivalTime: 06 Jul 2005 10:32:35.0450 (UTC) FILETIME=[062E0DA0:01C58216]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

Seisho,

I have a question on this draft:

In section 1 there is the following stated requirement:
"A P2MP TE LSP will be protected by fast error recovery mechanisms to
minimize disconnection of a P2MP service."

Which is obviously sensible, and of course implies that all the defect
cases of interest can be detected and the appropriate consequent actions
taken.  Note this should include defects of this layer network and not
just defects that arise in lower layer networks.  And remember....the
links between nodes in this layer network are provided by (p2p) trails
in a lower layer network....and this client/server relationship recurses
to the duct.  The point I am making here is that IF the lower layer
network has decent OAM itself you should get some indication of failure
from this, but this is over/above any defects you detect in this layer
network either from (i) lower layer defects or (ii) defects arising in
this layer network (which of course cannot be detected at all in any
lower layer network).


Yet it says in section 1.1 that a 'non-objective' is:
"OAM for P2MP LSPs"

Can someone please explain this apparent contradiction?


regards, Neil

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls