Re: [trill] New draft: draft-mizrahi-trill-loss-delay-00

Gagan Mohan Goel <Gagan_Goel@infosys.com> Tue, 19 February 2013 08:24 UTC

Return-Path: <Gagan_Goel@infosys.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CCE21F8BA1 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 00:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eoRezSKJx4CD for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 00:24:47 -0800 (PST)
Received: from KECGATE03.infosys.com (kecgate03.infosys.com [122.98.10.31]) by ietfa.amsl.com (Postfix) with ESMTP id 9870C21F8BC9 for <trill@ietf.org>; Tue, 19 Feb 2013 00:24:46 -0800 (PST)
X-TM-IMSS-Message-ID: <3932d3e70005aa1b@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.1) id 3932d3e70005aa1b ; Tue, 19 Feb 2013 13:47:50 +0530
Received: from BLRKECHUB08.ad.infosys.com (10.66.236.138) by blrkechub04.ad.infosys.com (10.66.236.44) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 19 Feb 2013 13:54:26 +0530
Received: from BLRKECMBX23.ad.infosys.com ([fe80::d9f9:2028:fd8:1e35]) by BLRKECHUB08.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 13:54:25 +0530
From: Gagan Mohan Goel <Gagan_Goel@infosys.com>
To: Tal Mizrahi <talmi@marvell.com>
Thread-Topic: New draft: draft-mizrahi-trill-loss-delay-00
Thread-Index: Ac4N5mrEG1XxBAnYSvSlgxyFBe7MxwAkmsFg
Date: Tue, 19 Feb 2013 08:24:25 +0000
Message-ID: <06D3FFFAA621E5459625E5E757AE9A1B0B8D970A@BLRKECMBX23.ad.infosys.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.236.169]
Content-Type: multipart/alternative; boundary="_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D970ABLRKECMBX23adin_"
MIME-Version: 1.0
Cc: "tsenevir@cisco.com" <tsenevir@cisco.com>, "Donald Eastlake \(d3e3e3@gmail.com\)" <d3e3e3@gmail.com>, "Samer Salam \(ssalam\) \(ssalam@cisco.com\)" <ssalam@cisco.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] New draft: draft-mizrahi-trill-loss-delay-00
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 08:24:50 -0000

Hi Tal,

Following are my views on the draft http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay.

1) Section 4.2.3 SLR Message Reception

<snip>    The receiver computes the one-way packet delay with respect to a measurement interval. A measurement interval includes a sequence of
   1SLM message. The one-way packet delay is performed by comparing the counter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measurement interval (Figure 2):
<snip>

I understand that receiver can only calculate the one way packet loss (and not packet delay) with incoming SLM message. I think the above can be modified to:



 The receiver computes the one-way packet loss with respect to a measurement interval. A measurement interval includes a sequence of
   SLM message. The one-way packet loss is performed by comparing the counter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measurement interval (Figure 2):

2) 4.1.2<http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay-00#section-4.1.2>.2>. 1SLM Message Reception

<snip> The receiver MUST maintain a reception counter for each peer MEP and test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:



   o The 1SLM packet is destined to the current MEP.

   o The packet's MD level matches the MEP's MD level.

<snip>
May be another criteria that can be added to handle any transient network loop scenario:
Ø  Discard the message if counter received in the incoming 1SLM message is lower than current RX count for same testID.
Regards
Gagan Mohan Goel

From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of Tal Mizrahi
Sent: Monday, February 18, 2013 8:17 PM
To: trill@ietf.org
Cc: tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer Salam (ssalam) (ssalam@cisco.com)
Subject: [trill] New draft: draft-mizrahi-trill-loss-delay-00

Hi,

We have uploaded a new draft titled "Loss and Delay Measurement in TRILL".

http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay

Comments will be welcome.

Thanks,
Tal.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***