Re: [mpls] Feedback request: draft on IP/MPLS transmission interruption
"Adrian Farrel" <adrian@olddog.co.uk> Tue, 10 July 2012 12:20 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C20221F8702 for <mpls@ietfa.amsl.com>; Tue, 10 Jul 2012 05:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.342
X-Spam-Level:
X-Spam-Status: No, score=-1.342 tagged_above=-999 required=5 tests=[AWL=-1.044, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_TOOL=2.3]
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 tOb5-kwgjgZ8 for <mpls@ietfa.amsl.com>; Tue, 10 Jul 2012 05:20:33 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 6174E21F86CA for <mpls@ietf.org>; Tue, 10 Jul 2012 05:20:32 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q6ACKmGZ004563; Tue, 10 Jul 2012 13:20:48 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q6ACKj6l004533 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 10 Jul 2012 13:20:47 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org
Date: Tue, 10 Jul 2012 13:20:47 +0100
Message-ID: <01da01cd5e96$70cab2d0$52601870$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01DB_01CD5E9E.D293D5C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1elhsIuJH/M9tvQU6ePkRCk3kYzA==
Content-Language: en-gb
Cc: 'Fan Peng' <fanpeng@chinamobile.com>, lilianyuan@chinamobile.com, ietf@cdl.asgaard.org
Subject: Re: [mpls] Feedback request: draft on IP/MPLS transmission interruption
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 10 Jul 2012 12:20:33 -0000
I think the MPLS WG should look at this I-D as well. Feedback to the authors or on the OPSAWG list, please. Adrian From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Fan Peng Sent: 10 July 2012 05:52 To: opsawg@ietf.org Cc: ietf@cdl.asgaard.org; lilianyuan@chinamobile.com Subject: [OPSAWG] Feedback request: draft on IP/MPLS transmission interruption Dear all, We have just updated the draft on IP/MPLS transmission interruption to 01 version, and we would like to hear comments from you. http://tools.ietf.org/html/draft-fan-opsawg-transmission-interruption-01 We presented the last version in Paris hoping the industry could discuss the problem of whether the sub-50ms outage time requirement is suitable for IP/MPLS. We proposed at the meeting two principles for network and service design, configuration and operation: the IP/MPLS bearer should satisfy quality requirements of upper level services and applications, while services and applications should also take into account the intrinsic IP capabilities. We did analysis on softswitch and reached the IP interruption requirement of 3 sec. In this 01 version we added case of parameter configuration in SS7 network to illustrate principle 2 (adaptation to IP). We gave examples on SCTP and M2PA and delivered the concept that upper levels should be more tolerable to IP best effort to avoid frequent disconnection. Parameter configuration needs to consider both requirement of application and nature of IP. Influence on service like SMS is also involved. Any feedback would be highly appreciated. Thanks and regards, Fan, Peng
- Re: [mpls] Feedback request: draft on IP/MPLS tra… Adrian Farrel
- Re: [mpls] Feedback request: draft on IP/MPLS tra… Loa Andersson