Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
"Luyuan Fang (lufang)" <lufang@cisco.com> Tue, 02 April 2013 12:46 UTC
Return-Path: <lufang@cisco.com>
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 40E8321F978D; Tue, 2 Apr 2013 05:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.846
X-Spam-Level:
X-Spam-Status: No, score=-8.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8]
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 RKDYmmUCKGOW; Tue, 2 Apr 2013 05:46:16 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 51E4621F978C; Tue, 2 Apr 2013 05:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9398; q=dns/txt; s=iport; t=1364906774; x=1366116374; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aYWAoLw7Z9Galx9QK5qGK8gyVfVKWtRUAJTH8kQGKFc=; b=bY25OYe3DIm96I7joRjmSdMKiI0qe/uELBof4IEGi9/83mkYlLyM0/AL d9IMveetJlgZVqH7px9fWKUV9lxT4kX/vEz1gWxHyIj5tSTOcBvFV3wFC JIdTFCvZdDP+YZcE3+x4WEDKgJzGeKMx8r9Rk0XhofEgq9jsewikqJShB Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJPSWlGtJV2d/2dsb2JhbABDgzuDILwkDXcWdIIfAQEBBAEBATE6CwwGAQgRAwEBAQEEBh0FBCULFAkIAgQBDQUIiAwMk16afgaCQpAQgR2MVYEFAgYgCwcCAgKCIThhA5gKj2yDC4FqPg
X-IronPort-AV: E=Sophos;i="4.87,393,1363132800"; d="scan'208";a="194076017"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 02 Apr 2013 12:46:13 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r32CkDf6018299 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Apr 2013 12:46:13 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.17]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 2 Apr 2013 07:46:13 -0500
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Doolan, Paul (NSN - US/Irving)" <paul.doolan@nsn.com>, Russ Housley <housley@vigilsec.com>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Index: AQHOLz4pe+S4mct/bEWgHAuKWl97qJjDKCGA///KQAA=
Date: Tue, 02 Apr 2013 12:46:12 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD93102CB82D@xmb-rcd-x03.cisco.com>
In-Reply-To: <0D9D63ECB53A1449B376D2196ADC34159B2D43@SGSIMBX001.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.21.92.107]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <C31E7A43632BB042BB2D8A589C04212B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 02 Apr 2013 12:46:17 -0000
Works for me. Thanks, Paul. Luyuan -----Original Message----- From: <Doolan>, "Paul (NSN - US/Irving)" <paul.doolan@nsn.com> Date: Tuesday, April 2, 2013 7:58 AM To: Luyuan Fang <lufang@cisco.com>, Russ Housley <housley@vigilsec.com>, "ietf@ietf.org" <ietf@ietf.org> Cc: "mpls@ietf.org" <mpls@ietf.org> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt> >Hi Luyuan, > >You wrote (in part): > >......since multiplexing of bursty sources is far more efficient over >traditional circuit-based >TDM technologies. > >Which is not true and probably not what you meant. > >A better formulation might be "since packet multiplexing of traffic from >bursty sources provides more efficient use of bandwidth than traditional >circuit-based TDM technologies". > >To be honest however, I'd cut the traditional and use only TDM (since >some 'circuit' based technologies also offer packet multiplexing) so I'd >reduce it to: > >A better formulation might be "since packet multiplexing of traffic from >bursty sources provides more efficient use of bandwidth than TDM >technologies". > > >cheers, >pd > > >-----Original Message----- >From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of >ext Luyuan Fang (lufang) >Sent: Monday, April 01, 2013 9:05 PM >To: Russ Housley; ietf@ietf.org >Cc: mpls@ietf.org >Subject: Re: [mpls] Last Call: ><draft-ietf-mpls-tp-use-cases-and-design-06.txt> > >Hi Russ, > >Thanks for your comments, very good points. >Sorry for the delay in replying, I was out of office. > > >The following is my proposed text for replacing the current first >paragraph of section 1.2. > > >Traditional transport technologies include SONET/SDH, TDM, and ATM. There >is a transition away from these transport technologies to new packet >technologies. >In addition to the ever increasing demand for bandwidth, the packet >technologies offer these key advantages: > > >Bandwidth efficiency: Transport technologies supports fixed Bandwidth >only, no packet statistical multiplexing, bandwidth is reserved in >transport >whether used or not by clients. Packet technologies support statistical >multiplexing, >this is the most important motivation for the transition from traditional >transport technologies to packet technologies. The proliferation of new >distributed applications which communicate with servers over the network >in a >bursty fashion has been driving the adoption of packet transport >techniques, since >multiplexing of bursty sources is far more efficient over traditional >circuit-based >TDM technologies. > > >Flexible data rate connections: Traditional transport connection >granularity >is limited to the rigid PDH or SONET hierarchy (e.g., DS1, DS3, OC3, OC12, >etc.). >Packet technologies support flexible data rate connections. The support of >finer data rate granularity is important for today¹s wireline and wireless >services and applications. > > >QoS support: While traditional transport, such as TDM transport has >very limited QoS support, packet transport can provide needed QoS >treatment for >IPTV, Voice and Video over IP applications. > > >The root cause for transport moving to packet transport is the shift >of application from TDM to packet. For example, Voice TDM to VoIP; Video >to >Video over IP; TDM access lines to Ethernet; TDM VPNs to IP VPNs and >Ethernet >VPNs. In addition, network convergence and technology refreshes demand for >common and flexible infrastructure that provides multiple services. > > >Thanks, >Luyuan > > > >-----Original Message----- >From: Russ Housley <housley@vigilsec.com> >Date: Saturday, March 23, 2013 3:16 PM >To: "ietf@ietf.org" <ietf@ietf.org> >Cc: "mpls@ietf.org" <mpls@ietf.org> >Subject: Re: [mpls] Last >Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt> > >>I wonder if the direction of Section 1.2 can be revised to make it more >>of an engineering document. >> >>It currently says: >> >> In recent years, the urgency for moving from traditional transport >> technologies, such as SONET/SDH, TDM, and ATM, to new packet >> technologies has been rising. This is largely due to the fast growing >> demand for bandwidth, which has been fueled by the following factors: >> ... >> >>Please consider an approach that describes the the reasons behind the >>transition from the network operator and network user perspectives: >> >> Traditional transport technologies include SONET/SDH, TDM, and ATM. >> There is a transition away from these transport technologies to new >> packet technologies. In addition to the ever increasing demand for >> bandwidth, the packet technologies offer these advantages: >> ... >> >>The fact that IP networks are being used for new applications and that >>the legacy devices are getting old does not motivate the transition to >>packet technologies. The advantages that packet technologies offer for >>these new applications is the thing that needs to be highlighted here, >>even if it is just a list of bullets. >> >>It seems like the only sentence that addresses this point in Section 1.2 >>is: "It streamlines the operation, reduces the overall complexity, and >>improves end-to-end convergence." >> >>Thanks, >> Russ >> >>On Jan 28, 2013, at 3:01 PM, The IESG wrote: >> >>> The IESG has received a request from the Multiprotocol Label Switching >>>WG >>> (mpls) to consider the following document: >>> - 'MPLS-TP Applicability; Use Cases and Design' >>> <draft-ietf-mpls-tp-use-cases-and-design-06.txt> as Informational RFC >>> >>> The IESG plans to make a decision in the next few weeks, and solicits >>> final comments on this action. Please send substantive comments to the >>> ietf@ietf.org mailing lists by 2013-02-11. Exceptionally, comments may >>>be >>> sent to iesg@ietf.org instead. In either case, please retain the >>> beginning of the Subject line to allow automated sorting. >>> >>> Abstract >>> >>> This document provides applicability, use case studies and network >>> design considerations for the Multiprotocol Label Switching Transport >>> Profile (MPLS-TP). The use cases include Metro Ethernet access and >>> aggregation transport, Mobile backhaul, and packet optical transport. >>> >>> The file can be obtained via >>> >>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/ >>> >>> IESG discussion can be tracked via >>> >>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/ >>>b >>>allot/ >>> >>> >>> No IPR declarations have been submitted directly on this I-D. >> >>_______________________________________________ >>mpls mailing list >>mpls@ietf.org >>https://www.ietf.org/mailman/listinfo/mpls >
- [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-a… The IESG
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cas… Russ Housley
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cas… Luyuan Fang (lufang)
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cas… Doolan, Paul (NSN - US/Irving)
- Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cas… Luyuan Fang (lufang)