[mpls] Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
Gerald Ash <gash5107@yahoo.com> Thu, 26 May 2011 16:51 UTC
Return-Path: <gash5107@yahoo.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 47671E0655 for <mpls@ietfa.amsl.com>; Thu, 26 May 2011 09:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.463
X-Spam-Level:
X-Spam-Status: No, score=-98.463 tagged_above=-999 required=5 tests=[AWL=2.175, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, USER_IN_WHITELIST=-100]
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 gKn-Hjma196S for <mpls@ietfa.amsl.com>; Thu, 26 May 2011 09:51:30 -0700 (PDT)
Received: from nm1-vm3.bullet.mail.ne1.yahoo.com (nm1-vm3.bullet.mail.ne1.yahoo.com [98.138.91.131]) by ietfa.amsl.com (Postfix) with SMTP id 89345E06FD for <mpls@ietf.org>; Thu, 26 May 2011 09:51:30 -0700 (PDT)
Received: from [98.138.90.51] by nm1.bullet.mail.ne1.yahoo.com with NNFMP; 26 May 2011 16:51:27 -0000
Received: from [98.138.89.246] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 26 May 2011 16:51:27 -0000
Received: from [127.0.0.1] by omp1060.mail.ne1.yahoo.com with NNFMP; 26 May 2011 16:51:27 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 368988.71360.bm@omp1060.mail.ne1.yahoo.com
Received: (qmail 89745 invoked by uid 60001); 26 May 2011 16:51:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1306428687; bh=0RrhAV1LY1ilwDBuu8cfkPjSeCUM9OiBRd7+LlCRmCs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=mfcTk2oxIGs9ge6S3mcrQLyuwghEoxAQqRjdO59ZIUWzdg9s1E5tzL7hUMTwzf6t1ir4lsGda0iDErbjtVsGa4uVlsfDQHn6W9LZPwxj7f0mo+ry6PH1uEBq7kUEOeQ664Wkyvib19w4zvQ7xGV3eARYc7s1dz0btSG0gr/KDak=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=VXe/8OCEeG0KKkFTGb3DaZljx6gF893l/NZbHGrX5sShd4g4ujJo/1ecsBFc907kKr4fetqh+KRNcd5zdOU/sAVbqrpVHO9vr+z6Fg9B6Pgk27DrBXx0PKE95M5Bnzwcr62Nx2iX7ZfRCDxULqqYqm2jCKojgD/qLgfQ4pUBryc=;
Message-ID: <285128.82087.qm@web125919.mail.ne1.yahoo.com>
X-YMail-OSG: 8kV5gCYVM1mnhywaa9Ft4Xgv7PS54KaW84.aUc9dKm0G6zG 1lFPbUDX.TEdtRMJtUEun2axEhY.fPJqTigj6aRTZedffpkWU0JRKfpnrkFl bnmZj33hTjBMJQn2I4btzkgPLGvb8nuv5VXFI7rXWQTBpfnr_Dc5aDg.5nbW u0C44OAhfLRSof4rv0p.hiVQPauET3NpldfQiH9EQH7PR9ZpAKczXImMakbv 7PFFfn4Q5p0BWvFWZH40EVIfvwic3WP4rz_L8hO_E5rA7XDEYAE9jq_pXEAB s9BCbohMUVVu1oJsZIVdVuFHnO3_mFvClj7gflQHcbMHrGz65lHP6dgvo0vQ RGnHP6NpRgNVKKZBgikG2f51l5g--
Received: from [71.233.102.170] by web125919.mail.ne1.yahoo.com via HTTP; Thu, 26 May 2011 09:51:27 PDT
X-Mailer: YahooMailClassic/14.0.1 YahooMailWebService/0.8.111.303096
Date: Thu, 26 May 2011 09:51:27 -0700
From: Gerald Ash <gash5107@yahoo.com>
To: rtgwg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1626380600-1306428687=:82087"
Cc: mpls@ietf.org
Subject: [mpls] Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
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: Thu, 26 May 2011 16:51:35 -0000
Hi, Adrian has suggested that the RTGWG and the MPLS WG review the draft "Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks", available at http://www.ietf.org/id/draft-ash-gcac-algorithm-spec-00.txt (abstract below). The underlying goal of the work is to specify an optional GCAC algorithm for IP/MPLS networks, to be adopted and implemented by vendors and service providers, that interoperates between vendor equipment and across multiple service provider domains. This would be analogous to the PNNI GCAC that was widely adopted and helped promote interoperability of ATM networks. In addition, the approach: o is based on CSPF, widely implemented by vendors o does NOT include aspects of CAC that might be considered vendor proprietary implementations, such as detailed path selection mechanisms o relies on available standard mechanisms for MPLS based networks, such as RSVP, DSTE, PCE... Comments appreciated. Thanks, Jerry From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ash-gcac-algorithm-spec-00.txt X-RSN: 1/0/935/34473/37870 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks Author(s) : G. Ash, D. McDysan Filename : draft-ash-gcac-algorithm-spec-00.txt Pages : 23 Date : 2011-1-11 This document presents a generic connection admission control (GCAC) reference model and algorithm for IP/MPLS-based networks. Service provider (SP) IP/MPLS networks need an MPLS GCAC mechanism, for example, to reject voice over Internet Protocol (VoIP) calls when additional calls would adversely affect calls already in progress. Without MPLS GCAC, connections on congested links will suffer degraded quality. The MPLS GCAC algorithm can be optionally implemented in vendor equipment and deployed by service providers. MPLS GCAC interoperates between vendor equipment and across multiple service provider domains. The MPLS GCAC algorithm uses available standard mechanisms for MPLS based networks, such as RSVP, DSTE, PCE, NSIS, DiffServ, and OSPF. The MPLS GCAC algorithm does not include aspects of CAC that might be considered vendor proprietary implementations, such as detailed path selection mechanisms. MPLS GCAC functions are implemented in a distributed manner to deliver the objective QoS for specified QoS constraints. The source is able to compute a source route with high likelihood that MPLS GCAC via elements along the selected path will in fact admit the request. MPLS GCAC is applicable to any service or flow that must meet an objective QoS (delay, jitter, packet loss rate) for a specified quantity of traffic. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ash-gcac-algorithm-spec-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ***** Click below to download the attachment(s) in this message: <A HREF="http://www.ietf.org/ibin/c5i?mid=6&gid=0&rid=8&k1=935&file=i-d-announce.37870.1.txt">Attachment: draft_ash_gcac_algorithm_spec_00.txt</A> (1K)
- [mpls] Generic Connection Admission Control (GCAC… Gerald Ash
- [mpls] Generic Connection Admission Control (GCAC… Gerald Ash
- Re: [mpls] Generic Connection Admission Control (… Azinger, Marla
- Re: [mpls] Generic Connection Admission Control (… Gerald Ash