[mpls] R: [mpls-tp] wg last call reslution in on mpls-tp-oam framework

"BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com> Sat, 02 October 2010 15:22 UTC

Return-Path: <italo.busi@alcatel-lucent.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C12E3A6DB2; Sat, 2 Oct 2010 08:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.995
X-Spam-Level:
X-Spam-Status: No, score=-3.995 tagged_above=-999 required=5 tests=[AWL=0.764, BAYES_05=-1.11, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, 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 rnj5kDf0I7Sl; Sat, 2 Oct 2010 08:22:43 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id B33B43A6C65; Sat, 2 Oct 2010 08:22:42 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o92FNQRV018384 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 2 Oct 2010 17:23:27 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Sat, 2 Oct 2010 17:23:26 +0200
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>, Loa Andersson <loa@pi.nu>
Date: Sat, 02 Oct 2010 17:23:27 +0200
Thread-Topic: [mpls-tp] wg last call reslution in on mpls-tp-oam framework
Thread-Index: Actd5IYU+9Ozpa3xTHe8aO9KewWcvQEYLm/g
Message-ID: <15740615FC9674499FBCE797B011623F0E2A2CD9@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <OFCBEE2FE8.72DD1D5C-ON482577AB.0008A6EA-482577AB.0008B6C5@zte.com.cn>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: it-IT, en-US
Content-Type: multipart/alternative; boundary="_000_15740615FC9674499FBCE797B011623F0E2A2CD9FRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls-tp-bounces@ietf.org" <mpls-tp-bounces@ietf.org>
Subject: [mpls] R: [mpls-tp] wg last call reslution in on mpls-tp-oam framework
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Oct 2010 15:22:44 -0000

Xiao Min,


Both one‑way and two‑way modes are common practice.



We therefore do not think we need to remove the two-way mode.



The two-way mode by definition estimates the minimum throughput of the two directions.



We understand that you are interested in getting the two individual available throughputs of the two directions. To address your point, we have clarified that:

“

In order to estimate the throughput of each direction uniquely, two one-way throughput estimation sessions have to be setup.
“

Italo

________________________________
Da: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] Per conto di xiao.min2@zte.com.cn
Inviato: lunedì 27 settembre 2010 3.36
A: Loa Andersson
Cc: mpls@ietf.org; MPLS-TP ad hoc team; mpls-tp-bounces@ietf.org; mpls-tp@ietf.org
Oggetto: Re: [mpls-tp] wg last call reslution in on mpls-tp-oam framework


Resend following comment without attachments.
=============================================

Loa and all,

I don't agree with the resolution on my comment 6 in the attached word document.

Cited words start======
6. In "section 6.3.1" the fifth paragraph, wrt the defined two-way throughput estimation which can only return the minimum of available throughput of the two directions, I'm not sure about the need from SP. Instead, to my understanding it's preferred to define two-way throughput estimation as a function which can return two individual available throughput of the two directioins, just as packet loss measurement.

Resolution: A note was added clarifying that two-way throughput estimation can only evaluate the minimum of available throughput of the two directions. In order to estimate the throughput in both directions, two one-way throughput estimation sessions have to be setup.
Cited words end=======

My comment intended to change the definition of two-way throughput estimation, at least not restrict it with the way that only evaluate the minimum of available throughput of the two directions, because I think that's unreasonable and I can't see the need for this kind of two-way throughput estimation from SP.

Best Regards,
Xiao Min


Loa Andersson <loa@pi.nu>
发件人:  mpls-tp-bounces@ietf.org

2010/09/23 20:02

收件人

"mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>

抄送



主题

[mpls-tp] wg last call reslution in on mpls-tp-oam framework










All,


the editors of the mpls-tp-oam-framework has sent us these two
word documents to describe how the outstanding wg lc comments has
been resolved.

/Loa

--


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                             +46 767 72 92 13
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp