Re: [mpls-tp] about open discussion about MIP MEP in MPLS-TP networks

John E Drake <jdrake@juniper.net> Thu, 02 December 2010 16:10 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C18DE28C157 for <mpls-tp@core3.amsl.com>; Thu, 2 Dec 2010 08:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level:
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5 tests=[AWL=0.360, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8SLB3Enl6klF for <mpls-tp@core3.amsl.com>; Thu, 2 Dec 2010 08:10:34 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by core3.amsl.com (Postfix) with ESMTP id CB92728C115 for <mpls-tp@ietf.org>; Thu, 2 Dec 2010 08:10:34 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTPfFPmbCj/14N+LiY3jaXYq7x7z+1qVC@postini.com; Thu, 02 Dec 2010 08:11:50 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 2 Dec 2010 08:10:22 -0800
From: John E Drake <jdrake@juniper.net>
To: Maarten Vissers <maarten.vissers@huawei.com>, 'Alexander Vainshtein' <Alexander.Vainshtein@ecitele.com>
Date: Thu, 2 Dec 2010 08:11:43 -0800
Thread-Topic: [mpls-tp] about open discussion about MIP MEP in MPLS-TP networks
Thread-Index: AcuSEqSsmVTVQTRgTP6v8C9tppW2jQACxtoQAANe7PAAAbnJIAABUv9A
Message-ID: <5E893DB832F57341992548CDBB33316398C549DEB0@EMBX01-HQ.jnpr.net>
References: <A1F769BC58A8B146B2EEA818EAE052A20964A4A6A7@GRFMBX702RM001.griffon.local> <143b01cb81bd$8c5c1c80$a5145580$@olddog.co.uk> <A3C5DF08D38B6049839A6F553B331C76D5CD91FFB5@ILPTMAIL02.ecitele.com> <15740615FC9674499FBCE797B011623F16B45326@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <A3C5DF08D38B6049839A6F553B331C76D5CD91FFBC@ILPTMAIL02.ecitele.com> <002f01cb8a33$07a01d10$16e05730$%vissers@huawei.com> <A3C5DF08D38B6049839A6F553B331C76D6B6ED93AA@ILPTMAIL02.ecitele.com> <15740615FC9674499FBCE797B011623F16BC6823@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <A3C5DF08D38B6049839A6F553B331C76D6B6ED977B@ILPTMAIL02.ecitele.com> <15740615FC9674499FBCE797B011623F16C23A97@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <A3C5DF08D38B6049839A6F553B331C76D6B78ED537@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C76D6B78ED538@ILPTMAIL02.ecitele.com> <4CF6172B.2070503@lab.ntt.co.jp> <001b01cb913c$d46eaf40$7d4c0dc0$%vissers@huawei.com> <4CF77F53.6090504@lab.ntt.co.jp> <007c01cb9236$1ebe5330$5c3af990$%vissers@huawei.com>
In-Reply-To: <007c01cb9236$1ebe5330$5c3af990$%vissers@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] about open discussion about MIP MEP in MPLS-TP networks
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 16:10:35 -0000

Snipped...

In the context of MPLS-TP what is a 'non-drop eligible frame'?  For one thing, we deal in packets.  For another, within a packet, where is this non-drop eligibility information carried?

Also, what does 'congestion on the links' mean?

Sent from my iPhone


> > [[[Sasha]]] Let's start from the fact that in packet (and, BTW, ATM)
> > networks, frames are discarded not only due
> > To bit errors, but also (and mainly) due to congestion. Congestion
> does
> > not have any analog in SDH.
> > In addition, indication of frames discarded due to CRC errors happens
> > only at the data link layer
> > (which MPLS-TP is not), and its indications are not forwarded
> anywhere.
> 
> [maarten] I am very much aware of the discarding due to congestion. I
> am
> also aware that in transport networks the expectation is that such
> discarding will be rare conditions for the non-drop eligible frames.
> 
> [maarten] The counting of transmitted and received frames and the
> computation of the difference presents the number of non-drop eligible
> frames that have been lost due to bit errors on the links and
> congestion on
> the links. The absence of an expected frame is a very good indication
> of
> such loss at an upstream point in the connection. The absence is
> forwarded
> by means of the transmitted and received counts.
> 
> I hope this clarifies my view a bit better.
> Regards,
> Maarten
> 
o/mpls-tp