[PWE3] heads up: Requirements for IP/MPLS network transmission interruption duration

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 12 March 2012 22:07 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C711221E811B; Mon, 12 Mar 2012 15:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.176
X-Spam-Level:
X-Spam-Status: No, score=-1.176 tagged_above=-999 required=5 tests=[AWL=-1.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u5h7IGpC0lXt; Mon, 12 Mar 2012 15:07:35 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id BB52D21E8127; Mon, 12 Mar 2012 15:07:34 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q2CM7Xqh026322; Mon, 12 Mar 2012 22:07:33 GMT
Received: from 950129200 ([90.84.144.248]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q2CM7O0I026241 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Mar 2012 22:07:31 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org, pwe3@ietf.org
Date: Mon, 12 Mar 2012 22:07:26 -0000
Message-ID: <037301cd009c$86ea4290$94bec7b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0374_01CD009C.86F16E80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac0AmstwFklFNpkJSWmctiWPHNLZ7A==
Content-Language: en-gb
Subject: [PWE3] heads up: Requirements for IP/MPLS network transmission interruption duration
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 22:07:37 -0000

Discussion should probably go to the Ops Area Working Group list.
 
Adrian
 
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of
fanpeng
Sent: 12 March 2012 15:24
To: opsawg@ietf.org; 'Bradner, Scott'; ietf@cdl.asgaard.org;
melinda.shore@gmail.com
Cc: 李连源
Subject: [OPSAWG] Requirements for IP/MPLS network transmission interruption
duration
 
Greetings all,
 
We have recently submitted a draft on transmission interruption duration
(draft-fan-opsawg-transmission-interuption-00
<http://datatracker.ietf.org/doc/draft-fan-opsawg-transmission-interuption/> ).
We felt it necessary to make requirements for the interruption duration since
there is no consensus on it yet in the industry. We primarily analyzed
interruption criteria for softswitch voice, and research on LTE backhaul and
other kinds of service scenarios has been in progress.
 
We would like to hear from you feedbacks about this draft, e.g. whether or not
there should be such requirements or methodology for the analysis. Any comment
on it will be appreciated.
 
The following is a brief introduction:
 
Today's IP/MPLS network is widely used as a bearing network to carry diversified
packet switched services. The transmission qualities of these services are
closely related to the performance of bearing layers, as network failure, delay,
congestion and other abnormities will inevitably bring about service
interruption and user perception degradation. However, there is no consensus in
the industry on transmission interruption for IP/MPLS network up to now.  This
memo studies relationships between service performance and transmission
interruption duration in several scenarios, and is intended to reach a list of
requirements for these interruption duration criteria.
 
 
Best regards,                                 
 
Fan Peng