From internet-drafts@ietf.org Sun Jun 3 13:34:57 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88C421F8690; Sun, 3 Jun 2012 13:34:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 D6Er1sQgfBfG; Sun, 3 Jun 2012 13:34:57 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6115021F8564; Sun, 3 Jun 2012 13:34:57 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120603203457.24298.91715.idtracker@ietfa.amsl.com> Date: Sun, 03 Jun 2012 13:34:57 -0700 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-erp-10.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 20:34:58 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions W= orking Group of the IETF. Title : Diameter Support for the EAP Re-authentication Protocol = (ERP) Author(s) : Julien Bournelle Lionel Morand Sebastien Decugis Qin Wu Glen Zorn Filename : draft-ietf-dime-erp-10.txt Pages : 16 Date : 2012-06-03 The EAP Re-authentication Protocol (ERP) defines extensions to the Extensible Authentication Protocol (EAP) to support efficient re- authentication between the peer and an EAP Re-authentication (ER) server through a compatible authenticator. This document specifies Diameter support for ERP. It defines a new Diameter ERP application to transport ERP messages between an ER authenticator and the ER server, and a set of new AVPs that can be used to transport the cryptographic material needed by the re-authentication server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-erp-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-dime-erp-10.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-erp/ From jouni.nospam@gmail.com Mon Jun 4 23:38:09 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3588621F8743 for ; Mon, 4 Jun 2012 23:38:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 t6-QXGC43EnE for ; Mon, 4 Jun 2012 23:38:08 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 78B5121F8742 for ; Mon, 4 Jun 2012 23:38:08 -0700 (PDT) Received: by yenq13 with SMTP id q13so4086079yen.31 for ; Mon, 04 Jun 2012 23:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=hRItajY6FjE9zNXJydjSoyn9Xnt2OWTVNjS0YnDDcmM=; b=pmCdGbDM3CLIq+Z7l5IsfPheyBwYqoRBAj5LyOAL4vH6YHDLaBvEeRgTiZL1g3zACS aUBCaQkkEi1ME9Krq4uVJVSZvLb3gn+XhcrSPSJCWCMa15ayzjfTQZOV1JO7hyHlJF/d K4EkYJmH99XAistubStSZ3/Ncbn+UIZWhBiscZZkfY5kePyA6VhAOYpnmCfIxMXJrH8n 6AtdSrhrsi+KgM2PwFV78z2ueGezgkhxaUnRRf3n0OJzNmFvi3X52d7kLvXUzI+ssTyB g8GreEcclUpnPTKpGphEDGHlYrJMapMDbP0tWkskEQuLfOZDA7yL3P6ZdDvvQ+MYNkfR FZhQ== Received: by 10.50.158.168 with SMTP id wv8mr960591igb.24.1338878287914; Mon, 04 Jun 2012 23:38:07 -0700 (PDT) Received: from [10.255.131.48] ([194.251.119.201]) by mx.google.com with ESMTPS id ey7sm1105653igb.2.2012.06.04.23.38.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 23:38:05 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <857EB77C-46F2-4001-9319-E2D7EFDB0A65@estacado.net> Date: Tue, 5 Jun 2012 09:38:00 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <5B2EC1BD-4035-4972-826C-D7BB710582F0@gmail.com> References: <5CD8EEAD-FD51-405F-AFE5-CC8CB372BEE9@gmail.com> <0CC419BA-6822-48E6-B1F8-D2DF7FA712D1@estacado.net> <8800ADBA-666A-45C5-9CC4-6B1A819C6E79@gmail.com> <37B40FC0-20FB-47D6-BBB4-D3B2BBB82F34@estacado.net> <0866D5BC-8CC9-46E7-BEF1-9AD4CA1207B1@gmail.com> <857EB77C-46F2-4001-9319-E2D7EFDB0A65@estacado.net> To: Eric McMurry X-Mailer: Apple Mail (2.1084) Cc: dime@ietf.org Subject: Re: [Dime] Diameter Overload Control Requirements X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 06:38:09 -0000 Hi Eric, Sorry for the delay.. I was occupied with other stuff. On May 31, 2012, at 4:42 PM, Eric McMurry wrote: > Hey Jouni, >=20 > On May 31, 2012, at 3:32 , jouni korhonen wrote: >=20 >> Hi Eric, >>=20 >> On May 31, 2012, at 12:11 AM, Eric McMurry wrote: >>=20 >>>=20 >>> On May 30, 2012, at 16:01 , Jouni wrote: >>>=20 >>>> Hi, >>>>=20 >>>> On May 30, 2012, at 9:06 PM, Eric McMurry wrote: >>>>=20 >>>>> Thanks for the comments Jouni. responses inline. >>>>>=20 >>>>> On May 30, 2012, at 10:21 , jouni korhonen wrote: >>>>=20 >>>>>> My reading of the solution requirements is that it is already = decided that extending >>>>>> base protocol is the way to go. Basically req-2 states this. I = don't think this is >>>>>> particularly good for a requirements document. >>>>>=20 >>>>> That part of req 2 was intended as an example and does not use = requirement language, so I agree with you that it should not be a direct = requirement. That said, addressing this in the base makes sense to me = and helps address several of the requirements. >>>>=20 >>>> Well, "MUST be useable with any existing or future.." and >>>> "MUST NOT require specification changes for existing.." basically >>>> rule out anything that you can stuff into CCF or existing commands >>>> in specs world. So I am left only with base protocol level options. >>>> Just language tweaking.. >>>>=20 >>>=20 >>> I think those requirements could be met without base level changes. = Perhaps I am misunderstanding your point though. Do you think that = working with existing and future >>> applications and not requiring changes to existing applications are = unreasonable requirements? >>=20 >> No. Definitely not. I was just saying, the req-2 does not, as written >> now, give you any other choice than extend or leverage the base >> protocol. I am not comfortable with that -- as a requirement to be >> documented. >=20 > So if we take off the last sentence (the one that refers to the base = protocol) would that allay your concern? That is a change for better, although it still does not change the outcome of the req-2 that much. However, if no one else sees an issue with this, we can leave the changes to the deletion of the last = sentence. We can always revisit the text later ;) - Jouni >=20 > Thanks, >=20 > Eric >=20 From emcmurry@estacado.net Tue Jun 5 09:29:34 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF6321F873E for ; Tue, 5 Jun 2012 09:29:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] 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 yeNXzAykQvFs for ; Tue, 5 Jun 2012 09:29:33 -0700 (PDT) Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8719021F870A for ; Tue, 5 Jun 2012 09:29:31 -0700 (PDT) Received: from embp.mcmurry.home (cpe-76-184-161-215.tx.res.rr.com [76.184.161.215]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q55GTLuj056381 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 5 Jun 2012 11:29:26 -0500 (CDT) (envelope-from emcmurry@estacado.net) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Eric McMurry In-Reply-To: <5B2EC1BD-4035-4972-826C-D7BB710582F0@gmail.com> Date: Tue, 5 Jun 2012 11:29:16 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5CD8EEAD-FD51-405F-AFE5-CC8CB372BEE9@gmail.com> <0CC419BA-6822-48E6-B1F8-D2DF7FA712D1@estacado.net> <8800ADBA-666A-45C5-9CC4-6B1A819C6E79@gmail.com> <37B40FC0-20FB-47D6-BBB4-D3B2BBB82F34@estacado.net> <0866D5BC-8CC9-46E7-BEF1-9AD4CA1207B1@gmail.com> <857EB77C-46F2-4001-9319-E2D7EFDB0A65@estacado.net> <5B2EC1BD-4035-4972-826C-D7BB710582F0@gmail.com> To: jouni korhonen X-Mailer: Apple Mail (2.1278) Cc: dime@ietf.org Subject: Re: [Dime] Diameter Overload Control Requirements X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 16:29:34 -0000 works for me. Thanks! Eric On Jun 5, 2012, at 1:38 , jouni korhonen wrote: > Hi Eric, >=20 > Sorry for the delay.. I was occupied with other stuff. >=20 >=20 > On May 31, 2012, at 4:42 PM, Eric McMurry wrote: >=20 >> Hey Jouni, >>=20 >> On May 31, 2012, at 3:32 , jouni korhonen wrote: >>=20 >>> Hi Eric, >>>=20 >>> On May 31, 2012, at 12:11 AM, Eric McMurry wrote: >>>=20 >>>>=20 >>>> On May 30, 2012, at 16:01 , Jouni wrote: >>>>=20 >>>>> Hi, >>>>>=20 >>>>> On May 30, 2012, at 9:06 PM, Eric McMurry wrote: >>>>>=20 >>>>>> Thanks for the comments Jouni. responses inline. >>>>>>=20 >>>>>> On May 30, 2012, at 10:21 , jouni korhonen wrote: >>>>>=20 >>>>>>> My reading of the solution requirements is that it is already = decided that extending >>>>>>> base protocol is the way to go. Basically req-2 states this. I = don't think this is >>>>>>> particularly good for a requirements document. >>>>>>=20 >>>>>> That part of req 2 was intended as an example and does not use = requirement language, so I agree with you that it should not be a direct = requirement. That said, addressing this in the base makes sense to me = and helps address several of the requirements. >>>>>=20 >>>>> Well, "MUST be useable with any existing or future.." and >>>>> "MUST NOT require specification changes for existing.." basically >>>>> rule out anything that you can stuff into CCF or existing commands >>>>> in specs world. So I am left only with base protocol level = options. >>>>> Just language tweaking.. >>>>>=20 >>>>=20 >>>> I think those requirements could be met without base level changes. = Perhaps I am misunderstanding your point though. Do you think that = working with existing and future >>>> applications and not requiring changes to existing applications are = unreasonable requirements? >>>=20 >>> No. Definitely not. I was just saying, the req-2 does not, as = written >>> now, give you any other choice than extend or leverage the base >>> protocol. I am not comfortable with that -- as a requirement to be >>> documented. >>=20 >> So if we take off the last sentence (the one that refers to the base = protocol) would that allay your concern? >=20 > That is a change for better, although it still does not change the > outcome of the req-2 that much. However, if no one else sees an issue > with this, we can leave the changes to the deletion of the last = sentence. > We can always revisit the text later ;) >=20 > - Jouni >=20 >=20 >=20 >=20 >>=20 >> Thanks, >>=20 >> Eric >>=20 >=20 From trac+dime@trac.tools.ietf.org Wed Jun 6 14:30:07 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003B121F8548 for ; Wed, 6 Jun 2012 14:30:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 eNErv3XciPUf for ; Wed, 6 Jun 2012 14:30:06 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 161F521F8541 for ; Wed, 6 Jun 2012 14:30:05 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1ScNna-0000jC-Rc; Wed, 06 Jun 2012 17:29:51 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "dime issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: dime@ietf.org, jouni.nospam@gmail.com X-Trac-Project: dime Date: Wed, 06 Jun 2012 21:29:50 -0000 X-URL: http://tools.ietf.org/wg/dime/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/5#comment:1 Message-ID: <079.a305d91bf84f4c5ea434538a3d3d6ebc@trac.tools.ietf.org> References: <064.5aee3d1dbf7b6bc73916072b31fe4db8@trac.tools.ietf.org> X-Trac-Ticket-ID: 5 In-Reply-To: <064.5aee3d1dbf7b6bc73916072b31fe4db8@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: dime@ietf.org, jouni.nospam@gmail.com, dime-chairs@tools.ietf.org X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] [dime] #5: review of realm-based-redirect X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Reply-To: dime@ietf.org List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 21:30:07 -0000 #5: review of realm-based-redirect Changes (by jouni.nospam@…): * cc: jouni.nospam@… (added) * status: new => closed * resolution: => fixed -- ----------------------------------+--------------------- Reporter: jouni.nospam@… | Owner: dime@… Type: defect | Status: closed Priority: major | Milestone: Component: realm-based-redirect | Version: Severity: In WG Last Call | Resolution: fixed Keywords: | ----------------------------------+--------------------- Ticket URL: dime From ruibing_hao@cable.comcast.com Thu Jun 7 06:31:54 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 750A521F88B5 for ; Thu, 7 Jun 2012 06:31:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.23 X-Spam-Level: X-Spam-Status: No, score=-105.23 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 HM2Qp1-WZAwx for ; Thu, 7 Jun 2012 06:31:53 -0700 (PDT) Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D4AB821F8705 for ; Thu, 7 Jun 2012 06:31:52 -0700 (PDT) Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.20285914; Thu, 07 Jun 2012 07:15:35 -0600 Received: from PACDCEXMB01.cable.comcast.com ([169.254.1.45]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%13]) with mapi id 14.02.0283.003; Thu, 7 Jun 2012 09:31:45 -0400 From: "Hao, Ruibing" To: "dime@ietf.org" Thread-Topic: Another use case for draft-ietf-dime-realm-based-redirect Thread-Index: AQHNRLHhwgwtUWmQ9UuOi17MNAnkIw== Date: Thu, 7 Jun 2012 13:31:44 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.13.0.110805 x-originating-ip: [24.40.55.73] Content-Type: multipart/alternative; boundary="_000_CBF6257E19743RuibingHaocablecomcastcom_" MIME-Version: 1.0 Subject: Re: [Dime] Another use case for draft-ietf-dime-realm-based-redirect X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2012 13:31:54 -0000 --_000_CBF6257E19743RuibingHaocablecomcastcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Tina and Tom, Here is a summary of the challenge we are facing on Sh/Dh interface in a 3G= PP IMS deployment where we need to support SLF and Realm-based routing on A= S on Sh interface at the same time. The subscriber data is provisioned in a geo-redundant HSS cluster, each AS = need to maintain redundant Diameter Sh links to both cluster nodes and make= use of realm-based routing to always go to the local HSS cluster node when= it is available. There can be multiple geo-redundant HSS clusters, SLF ca= n be used to determine which HSS cluster stores the subscriber's service da= ta. With the realm-based redirect proposal, we should be able to maintain t= he local realm-based routing configuration on each AS. This might be another good use case for the internet-draft you guys are pro= posing. Ruibing Hao Principal Engineer Comcast Cable One Comcast Center Philadelphia, PA 19103 Tel: 215-286-3991(O) --_000_CBF6257E19743RuibingHaocablecomcastcom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Tina and Tom,

Here is a summary of the challenge we are facing on Sh/Dh interf= ace in a 3GPP IMS deployment where we need to support SLF and Realm-based r= outing on AS on Sh interface at the same time. 

The subscriber data is provisioned in a geo-redundant HSS cluste= r, each AS need to maintain redundant Diameter Sh links to both cluster nod= es and make use of realm-based routing to always go to the local HSS cluste= r node when it is available.  There can be multiple geo-redundant HSS clusters, SLF can be used to determine w= hich HSS cluster stores the subscriber's service data. With the realm-based= redirect proposal, we should be able to maintain the local realm-based rou= ting configuration on each AS. 

This might be another good use case for the internet-draft you g= uys are proposing. 

Ruibing Hao
Principal= Engineer
Comcast C= able
One Comcast Center
Philadelphia, PA 19103
Tel: 215-286-3991(O)
--_000_CBF6257E19743RuibingHaocablecomcastcom_-- From jouni.nospam@gmail.com Mon Jun 11 04:14:01 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB41921F856C for ; Mon, 11 Jun 2012 04:14:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.74 X-Spam-Level: X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1] 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 Dyti+kV5dQ5w for ; Mon, 11 Jun 2012 04:14:01 -0700 (PDT) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 466FA21F8569 for ; Mon, 11 Jun 2012 04:14:01 -0700 (PDT) Received: by qadz3 with SMTP id z3so1870464qad.10 for ; Mon, 11 Jun 2012 04:14:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=p6XPfeuByrP44kZy9ax3Xh3GQPyXGefjc4AurEyojTA=; b=FN0O6ELIUdAMDZV4j+MdkLLhDNmVZyDTudYWlB3lEBjK8QdUn1Hw+u+jlNNW3U95pX A+pTv4YYi5FIzphwY6jbK7jilm91BTcSP7qdbqILDkrCXjBXo2VmFStcYpYBGGLoWQOJ npyydz888HTSO/v1seg0mK5hMS76cPRhdzMAbiWsPh0v9fOGfMCHJr39ZyESneVg8bv8 cDJeWwh8vAfq+fkWaUFMr7V5coR/6hJyM5fdu0CXrUMJCX6SvnW55Td4TLkVQGeQnBBR Iqf47EqjZ5W53UBhn1P6mFESbF6rwSrUAhpET+TfuC1o8DDqCYNbjkFBJ59/fsL94b4C Fm1w== Received: by 10.229.137.140 with SMTP id w12mr6125766qct.133.1339413240693; Mon, 11 Jun 2012 04:14:00 -0700 (PDT) Received: from [10.255.129.125] ([194.251.119.201]) by mx.google.com with ESMTPS id bk12sm634941qab.6.2012.06.11.04.13.59 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jun 2012 04:14:00 -0700 (PDT) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 11 Jun 2012 14:13:56 +0300 Message-Id: <788F0AE8-8A2B-4279-B5EC-9D08DD8F33AE@gmail.com> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: dime-chairs@tools.ietf.org Subject: [Dime] Agenda Items and logistics for Dime WG meeting in Vancouver X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 11:14:01 -0000 Folk, We have again requested 2h WG slot for Dime. Feel free to propose agenda items. Send a mail to the chairs with a topic, an abstract and presentation time wish. One very potential agenda item will be Diameter Overload Control, which stirred some interesting discussion on the mailing list already. Furthermore, we solicit volunteers for note takers and jabber scribes. - Jouni From jouni.nospam@gmail.com Wed Jun 20 23:18:58 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 863E921F85A1 for ; Wed, 20 Jun 2012 23:18:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 uMhR5IaT69Kc for ; Wed, 20 Jun 2012 23:18:56 -0700 (PDT) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 93E0F21F85A3 for ; Wed, 20 Jun 2012 23:18:56 -0700 (PDT) Received: by eekd4 with SMTP id d4so56064eek.31 for ; Wed, 20 Jun 2012 23:18:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=nxAusOahZeuATJ4T6IQedTP39NjN48bBlngrtj6nIeM=; b=blFZmlno7RgAyNfesD9SfumHlO7Dp7vNHrF4mMsrRmVPfPYtoRTjesXqMDBVCa0m+s u3wqh3lfQKwiBXYfdEtWljHmZgD0vLzDRXgF6QB1MG61LXRjc/09WWnb/B/xUo8xqGSF Vv0f9alY5ItF2B7VT3gUqChl30UxDnbpg/QhqYRzJ8/SYa4A67MXPggq4j2PEC2L2Zdn 1nvDnmuW2AV3e/jCfunu5kmsmD8m/wqgqbPj1RsTZJOiMFao1tSHUEuGjnDmw56abzE+ UjlDF0kmRUZuQnoGePPNnjgs7y5VWQ90f+cmlYoEYLNS3oaMoBMJcjiOZGZxBSGs+UzR CxhQ== Received: by 10.14.48.4 with SMTP id u4mr5585638eeb.207.1340259535657; Wed, 20 Jun 2012 23:18:55 -0700 (PDT) Received: from ?IPv6:2001:1bc8:101:f101:226:bbff:fe18:6e9c? ([2001:1bc8:101:f101:226:bbff:fe18:6e9c]) by mx.google.com with ESMTPS id c42sm99290217eeb.2.2012.06.20.23.18.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Jun 2012 23:18:53 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: jouni korhonen In-Reply-To: <4C639074-1D3C-44E8-B2EB-D602681818A4@gmail.com> Date: Thu, 21 Jun 2012 09:18:46 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <54D896C7-034B-49F9-B1A7-4D399E9263B0@gmail.com> References: <4C639074-1D3C-44E8-B2EB-D602681818A4@gmail.com> To: dime@ietf.org X-Mailer: Apple Mail (2.1084) Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] Call for WG adoption: draft-jones-diameter-group-signaling-01 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 06:18:58 -0000 Folks, The one week period has passed ;-) There was no objection to adopt = draft-jones-diameter-group-signaling-01 as a basis for the WG document & solution. Mark, go ahead and post the draft-ietf-dime-diameter-group-signaling-00. - Jouni & Lionel On Apr 1, 2012, at 10:20 PM, jouni korhonen wrote: >=20 > Folks, >=20 > During the Dime WG meeting in Paris we decided to adopt = draft-jones-diameter-group-signaling-01 > "Diameter Group Signaling" as a working group I-D. The I-D is an input = for the charter mile stone > 'Protocol extension for bulk and group signaling'. >=20 > This mail starts a one week verification for the adoption. If you have = strong concerns that the=20 > draft-jones-diameter-group-signaling-01 is not appropriate as a = _basis_ for the solution, then > express your concerns on the mailing list by 8th April. >=20 > - Jouni & Lionel >=20 >=20 From jouni.korhonen@iki.fi Thu Jun 21 04:17:44 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C55D21F8548 for ; Thu, 21 Jun 2012 04:17:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 FQH8EXcdRGCb for ; Thu, 21 Jun 2012 04:17:44 -0700 (PDT) Received: from vs16.mail.saunalahti.fi (vs16.mail.saunalahti.fi [62.142.117.197]) by ietfa.amsl.com (Postfix) with ESMTP id CE99021F853A for ; Thu, 21 Jun 2012 04:17:42 -0700 (PDT) Received: from vams (localhost [127.0.0.1]) by vs16.mail.saunalahti.fi (Postfix) with SMTP id DF80C2005C for ; Thu, 21 Jun 2012 14:17:38 +0300 (EEST) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by vs16.mail.saunalahti.fi (Postfix) with ESMTP id C3E092005C for ; Thu, 21 Jun 2012 14:17:38 +0300 (EEST) Received: from a88-114-69-131.elisa-laajakaista.fi (a88-114-69-131.elisa-laajakaista.fi [88.114.69.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id C62B7151ABA for ; Thu, 21 Jun 2012 14:17:37 +0300 (EEST) From: jouni korhonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 21 Jun 2012 14:17:36 +0300 Message-Id: <1BDC22A3-83B9-491D-A8AA-CF9CD718265A@iki.fi> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Mailman-Approved-At: Thu, 21 Jun 2012 06:11:44 -0700 Subject: [Dime] RFC3588bis cipher suite question X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 13:10:36 -0000 Folks, In Section 13.1 we have the following text: Diameter nodes MUST be able to negotiate the following TLS/TCP and DTLS/SCTP cipher suites: TLS_RSA_WITH_RC4_128_MD5 TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA Diameter nodes SHOULD be able to negotiate the following TLS/TCP and DTLS/SCTP cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA Note that that it is quite possible that support for the TLS_RSA_WITH_AES_128_CBC_SHA ciphersuite will be REQUIRED at some future date. Diameter nodes MAY negotiate other TLS/TCP and DTLS/ SCTP cipher suites. I know this is a bit late in the pipe but.. but RFC6347 (DTLS v1.2) has the following statement: The only stream cipher described in TLS 1.2 is RC4, which cannot be randomly accessed. RC4 MUST NOT be used with DTLS. That does not go too well with the RFC3588bis MUST for RC4 stream ciphers. Also RFC5246 states: In the absence of an application profile standard specifying otherwise, a TLS-compliant application MUST implement the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA.. Can we understand that the current text in RFC3588bis serves as the profile and the SHOULD there is then OK from the RFC5246 point of view? - Jouni From emcmurry@estacado.net Thu Jun 21 06:18:43 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE4621F861B for ; Thu, 21 Jun 2012 06:18:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 ueGZiDzb192N for ; Thu, 21 Jun 2012 06:18:43 -0700 (PDT) Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8E02721F85C2 for ; Thu, 21 Jun 2012 06:18:40 -0700 (PDT) Received: from embp.mcmurry.home (cpe-76-184-161-215.tx.res.rr.com [76.184.161.215]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q5LDIYdb000839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 21 Jun 2012 08:18:38 -0500 (CDT) (envelope-from emcmurry@estacado.net) From: Eric McMurry Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 21 Jun 2012 08:18:29 -0500 Message-Id: <140EC8EF-DB2A-4112-9313-04C9A78119E8@estacado.net> To: dime@ietf.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [Dime] Diameter Overload Control Requirements update X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 13:18:43 -0000 An update has been submitted for the draft intended to address = requirements for overload control in Diameter: URL: = http://www.ietf.org/internet-drafts/draft-mcmurry-dime-overload-reqs-01.tx= t Status: = http://datatracker.ietf.org/doc/draft-mcmurry-dime-overload-reqs Htmlized: = http://tools.ietf.org/html/draft-mcmurry-dime-overload-reqs-01 Diff: = http://tools.ietf.org/rfcdiff?url2=3Ddraft-mcmurry-dime-overload-reqs-01 This update attempts to address all of the comments received on the list = so far, and adds some additional information to the front matter and = justification. From internet-drafts@ietf.org Fri Jun 22 14:11:35 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A3B11E80D5; Fri, 22 Jun 2012 14:11:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.45 X-Spam-Level: X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 dzeU-851VKR4; Fri, 22 Jun 2012 14:11:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAEB11E80A3; Fri, 22 Jun 2012 14:11:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.21 Message-ID: <20120622211134.28247.54205.idtracker@ietfa.amsl.com> Date: Fri, 22 Jun 2012 14:11:34 -0700 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-group-signaling-00.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 21:11:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Group Signaling Author(s) : Mark Jones Filename : draft-ietf-dime-group-signaling-00.txt Pages : 24 Date : 2012-06-22 Abstract: In large network deployments, a single Diameter peer can support over a million concurrent Diameter sessions. Recent use cases have revealed the need for Diameter peers to apply the same operation to a large group of Diameter sessions concurrently. The Diameter base protocol commands operate on a single session so these use cases could result in many thousands of command exchanges to enforce the same operation on each session in the group. In order to reduce signaling, it would be desirable to enable bulk operations on all (or part of) the sessions managed by a Diameter peer using a single or a few command exchanges. This document specifies the Diameter protocol extensions to achieve this signaling optimization. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-group-signaling There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-group-signaling-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Jun 22 20:17:07 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323D811E80BA; Fri, 22 Jun 2012 20:17:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.469 X-Spam-Level: X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 to6VL-py0kec; Fri, 22 Jun 2012 20:17:06 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A646221F849A; Fri, 22 Jun 2012 20:17:05 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.21 Message-ID: <20120623031705.30540.75705.idtracker@ietfa.amsl.com> Date: Fri, 22 Jun 2012 20:17:05 -0700 Cc: dime@ietf.org Subject: [Dime] I-D Action: draft-ietf-dime-rfc3588bis-34.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 03:17:07 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Diameter Maintenance and Extensions Worki= ng Group of the IETF. Title : Diameter Base Protocol Author(s) : Victor Fajardo Jari Arkko John Loughney Glen Zorn Filename : draft-ietf-dime-rfc3588bis-34.txt Pages : 154 Date : 2012-06-22 Abstract: The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility in both local and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services used by all Diameter applications. The Diameter base protocol as defined in this document obsoletes RFC 3588 and RFC 5719 and must be supported by all new Diameter implementations. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dime-rfc3588bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-dime-rfc3588bis-34 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-dime-rfc3588bis-34 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From ben@nostrum.com Mon Jun 25 15:18:00 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2BD21F8597 for ; Mon, 25 Jun 2012 15:18:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 zsfSiJSdFllt for ; Mon, 25 Jun 2012 15:18:00 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 010FC21F8596 for ; Mon, 25 Jun 2012 15:17:59 -0700 (PDT) Received: from [10.12.30.47] ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q5PMHwvU038952 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Jun 2012 17:17:58 -0500 (CDT) (envelope-from ben@nostrum.com) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Ben Campbell In-Reply-To: <140EC8EF-DB2A-4112-9313-04C9A78119E8@estacado.net> Date: Mon, 25 Jun 2012 17:17:58 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <220DC4C5-3DE6-4EA5-A33E-8B387E26FCC2@nostrum.com> References: <140EC8EF-DB2A-4112-9313-04C9A78119E8@estacado.net> To: dime@ietf.org X-Mailer: Apple Mail (2.1278) Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism) Cc: dime-chairs@tools.ietf.org Subject: Re: [Dime] Diameter Overload Control Requirements update X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 22:18:00 -0000 Hi everyone, We thank everyone who has offered feedback and support so far. This = revision attempts to address the feedback we received. We would = appreciate it if people can confirm whether we've succeeded in that = attempt. The authors would also like to get feedback on whether the this draft, = as well as any resulting solution, would be an appropriate effort for = the DIME working group. We believe that "overload control" reasonable = fits the "maintenance of the base protocol" aspect of the current DIME = charter, and that this draft makes a reasonable start towards defining = the problem and requirements. Do others agree?=20 Thanks! Ben. On Jun 21, 2012, at 8:18 AM, Eric McMurry wrote: > An update has been submitted for the draft intended to address = requirements for overload control in Diameter: >=20 > URL: = http://www.ietf.org/internet-drafts/draft-mcmurry-dime-overload-reqs-01.tx= t > Status: = http://datatracker.ietf.org/doc/draft-mcmurry-dime-overload-reqs > Htmlized: = http://tools.ietf.org/html/draft-mcmurry-dime-overload-reqs-01 > Diff: = http://tools.ietf.org/rfcdiff?url2=3Ddraft-mcmurry-dime-overload-reqs-01 >=20 > This update attempts to address all of the comments received on the = list so far, and adds some additional information to the front matter = and justification. >=20 >=20 > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime From Internet-Drafts@ietf.org Thu Jun 28 14:24:42 2012 Return-Path: X-Original-To: dime@ietfa.amsl.com Delivered-To: dime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2110821F8513; Thu, 28 Jun 2012 14:24:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 iXoYRPZWLIfZ; Thu, 28 Jun 2012 14:24:41 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBB021F8505; Thu, 28 Jun 2012 14:24:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.21p1 Message-ID: <20120628212440.15507.23974.idtracker@ietfa.amsl.com> Date: Thu, 28 Jun 2012 14:24:40 -0700 Cc: dime@ietf.org Subject: [Dime] I-D ACTION:draft-ietf-dime-priority-avps-06.txt X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2012 21:24:42 -0000 --NextPart A new Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF. Title : Diameter Priority Attribute Value Pairs Author(s) : K. Carlberg, et al Filename : draft-ietf-dime-priority-avps Pages : 9 Date : June 28, 2012 This document defines Attribute-Value Pair (AVP) containers for various priority parameters for use with Diameter and the AAA framework. The parameters themselves are defined in several different protocols that operate at either the network or application layer. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dime-priority-avps-06.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. --NextPart Content-Type: Message/External-body; name="draft-ietf-dime-priority-avps"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2012-06-28142440.I-D@ietf.org> --NextPart--