Re: Re:[mpls] draft-yasukawa-mpls-p2mp-oam-reqs-01.txt to become a working group document?
"Adrian Farrel" <adrian@olddog.co.uk> Mon, 12 December 2005 11:40 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elm36-0007hj-Mg; Mon, 12 Dec 2005 06:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elm2z-0007gZ-Pq for mpls@megatron.ietf.org; Mon, 12 Dec 2005 06:40:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08840 for <mpls@ietf.org>; Mon, 12 Dec 2005 06:39:44 -0500 (EST)
Received: from relay3.mail.uk.clara.net ([80.168.70.143]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Elm3b-0008Rl-SZ for mpls@ietf.org; Mon, 12 Dec 2005 06:41:29 -0500
Received: from du-069-0198.access.clara.net ([217.158.132.198] helo=Puppy) by relay3.mail.uk.clara.net with esmtp (Exim 4.46) id 1Elm2g-000KUq-DZ; Mon, 12 Dec 2005 11:40:31 +0000
Message-ID: <057601c5ff11$5bb78d50$9d849ed9@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: chasey_ch <chasey_ch@indiatimes.com>, mpls@ietf.org
References: <200512111906.AAA01923@WS0005.indiatimes.com>
Subject: Re: Re:[mpls] draft-yasukawa-mpls-p2mp-oam-reqs-01.txt to become a working group document?
Date: Mon, 12 Dec 2005 11:44:03 -0000
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-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc:
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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
Hi Chasey, Thanks for the comments. > Subject: Re:[mpls] draft-yasukawa-mpls-p2mp-oam-reqs-01.txt to become > a working group document? > > few humble questions > (tell me if am wrong fundamentally): > > 1. why the draft doesnt talk about segment OAM though for PMP scalability > as an issue? Scalability is as much a requirement for P2MP as for P2P. In fact, since the nature of P2MP is that there are more egresses per LSP, scalability must be given considerably more attention. You specifically ask about "segment OAM" so I wondered if you were referring to a technique already described in draft-ietf-mpls-oam-requirements, but I can't find any reference there. So perhaps you are suggesting some new behaviors and requirements specific to P2MP? Maybe if you could spell out what you are thinking about in a little more detail we could consider incorporating it into a future version of the draft. > 2. why there is no mention of OAM procedure for backup tunnel > (especially for facility protection when one path can backup multiple > paths, hence should never go down ideally) I am not clear why your question is specific to P2MP. But I am also not clear why you single out facility backup tunnels as being more critical than other tunnels. The importance of a tunnel depends on the use to which it is put, and it is quite possible that many tunnels are more critical than facility backup tunnels. Further, your comment says that a facility backup tunnel "should never go down ideally". But you must observe that we are talking about OAM. OAM does not prevent tunnels from going down. It simply allows you to detect and isolate faults (conversely to monitor the continued absence of faults). Again, perhaps you could indicate what you would like to see described in the draft so that we can look at how to include it. Thanks, Adrian _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
- Re:[mpls] draft-yasukawa-mpls-p2mp-oam-reqs-01.tx… chasey_ch
- Re: Re:[mpls] draft-yasukawa-mpls-p2mp-oam-reqs-0… Adrian Farrel