From dime-bounces@ietf.org Fri Jan 13 02:02:22 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExIx4-0001xX-G4; Fri, 13 Jan 2006 02:02:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExIx3-0001x3-Jj for dime@megatron.ietf.org; Fri, 13 Jan 2006 02:02:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07264 for ; Fri, 13 Jan 2006 02:00:53 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ExJ4C-0006jV-IN for dime@ietf.org; Fri, 13 Jan 2006 02:09:46 -0500 Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0D6vTXV031264; Fri, 13 Jan 2006 08:57:33 +0200 Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jan 2006 09:02:00 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jan 2006 09:02:00 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 13 Jan 2006 09:01:59 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D01869B2A@esebe100.NOE.Nokia.com> Thread-Topic: Diameter Interop Thread-Index: AcYR+S5Atjg+flBQRluS02VXhnRbSQFoAwCQAB1myyA= To: X-OriginalArrivalTime: 13 Jan 2006 07:02:00.0363 (UTC) FILETIME=[3FFB07B0:01C6180F] X-Spam-Score: 0.4 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: quoted-printable Cc: dime@ietf.org Subject: [Dime] FW: Diameter Interop X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi all, I just got word that we have a host for the Diameter Interop.=20 I am pleased to inform you that Ulticom will host the upcoming=20 Diameter interop event.=20 I believe the site will be at Ulticom's office: Ulticom, Inc. 1020 Briggs Road Mt. Laurel, NJ 08054 USA=20 Looking at the calendar, I think starting Monday April 3rd & reserving=20 that week for the test would be good - just to avoid the Easter holiday. As I get more information on the logistics, etc. I will update the list. Additionally, I'd need feedback on the date and any requirements anyone would have. Additionally, we would need some volunteers to work-up test plans, test=20 cases. thanks, John _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Mon Jan 16 06:04:24 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyS9w-0000dU-Ak; Mon, 16 Jan 2006 06:04:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyS9u-0000c5-Gx; Mon, 16 Jan 2006 06:04:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03244; Mon, 16 Jan 2006 06:02:58 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EySHo-00049D-26; Mon, 16 Jan 2006 06:12:33 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k0GB4E2j009302; Mon, 16 Jan 2006 05:04:17 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Mon, 16 Jan 2006 12:04:12 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550915483F@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Aaa-Wg (E-mail)" , dime@ietf.org, nsis@ietf.org Date: Mon, 16 Jan 2006 12:04:13 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: "David Kessens \(E-mail\)" Subject: [Dime] Looking for candidates for (co-)chairing the (new) DIME WG X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org [posted to AAA, DIME and NSIS mailing lists since we expect that those mailing lists have the most relevant participants.] All, The new DIME WG (see charter at the bottom) has been approved by the IESG. The actual instantiation of the WG is pending the appointment of WG chair(s). The ADs have decided to write down a brief profile for the WG chair(s). We would like you to consider this profile and either nominate yourself or other people that you think that would fit well in this role by sending mail to the OPS ADs. ( and ). We do not intend to disclose the names of the nominees in public, but we will probably sollicit for feedback with various other people. If you have a problem with your name being mentioned in this context, pls let us know. Note that this profile is written for a somewhat ideal candidate. We fully realize that such people are probably non-existent, so don't hesitate to nominate somebody who in your opinion would fit this role quite well but doesn't fit this profile 100%. And the intend is to select two co-chairs that can complement each other and work together. As for the profile: - Good management and process skills, including but not limited to choosing and supervising editors, commitment and followthrough on the charter, active management of the working group discussions, and handling IETF process steps in prompt fashion. - Good basic knowledge of the AAA protocols. That not only includes Diameter, but also Radius. - Understanding of the requirements/needs/applications of AAA protocols. Specifically, understanding the needs of other organizations (like 3GPP) is a useful asset. - Operational background/experience is very desirable. - Enough available time. For example, preferable not more than one other working chair role in IETF. - There is no requirement that the candidate has been an IETF working group chair before, but it helps if there is some evidence that the candidate can fullfill such a role (eg. other management role in other places than IETF etc.) We would like to receive your comments & nominations by Jan 30th 2006 and we plan to make a decision as soon as possible thereafter. It will be helpful if you indicate in your nomination mail how you or the nominated candidate fits this profile as best as possible. And last but not least, we would like to thank John Loughney for leading/guiding the work to develop the DIME WG charter. He also started a new mailing list: dime@ietf.org David Kessens & Bert Wijnen _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 05:12:51 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1hdz-0003WL-AK; Wed, 25 Jan 2006 05:12:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1hdx-0003V7-P8 for dime@megatron.ietf.org; Wed, 25 Jan 2006 05:12:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27981 for ; Wed, 25 Jan 2006 05:11:17 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1hnf-0002L7-4m for dime@ietf.org; Wed, 25 Jan 2006 05:22:53 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k0PACbf3021170 for ; Wed, 25 Jan 2006 04:12:38 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Wed, 25 Jan 2006 11:12:35 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550922C9A9@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: dime@ietf.org Date: Wed, 25 Jan 2006 11:12:35 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Subject: [Dime] Repeat: Looking for candidates for (co-)chairing the (new) DIME W G X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org [bcc: aaa-doctors, nsis WG, radiusext] Sofar, the number of reactions/nominations has been minimal. So do we not have people who are willing to work hard and chair this WG-to-be? Besides, I have not seen much discussion on the DIME WG mailing list lately. Is there no interest to discuss the 5 internet-drafts listed in the DIME WG charter? Does this all mean that there is no real support/willingness-to-work on this after all? It is easy to withdraw the WG at this stage. And non-activity or non-reaction to the poll for WG chairs is (for me) a good reason to cancel before we start. Bert -----Original Message----- From: owner-aaa-doctors@ops.ietf.org [mailto:owner-aaa-doctors@ops.ietf.org]On Behalf Of Wijnen, Bert (Bert) Sent: Monday, January 16, 2006 12:04 To: Aaa-Wg (E-mail); dime@ietf.org; nsis@ietf.org Cc: David Kessens (E-mail) Subject: Looking for candidates for (co-)chairing the (new) DIME WG [posted to AAA, DIME and NSIS mailing lists since we expect that those mailing lists have the most relevant participants.] All, The new DIME WG (see charter at the bottom) has been approved by the IESG. The actual instantiation of the WG is pending the appointment of WG chair(s). The ADs have decided to write down a brief profile for the WG chair(s). We would like you to consider this profile and either nominate yourself or other people that you think that would fit well in this role by sending mail to the OPS ADs. ( and ). We do not intend to disclose the names of the nominees in public, but we will probably sollicit for feedback with various other people. If you have a problem with your name being mentioned in this context, pls let us know. Note that this profile is written for a somewhat ideal candidate. We fully realize that such people are probably non-existent, so don't hesitate to nominate somebody who in your opinion would fit this role quite well but doesn't fit this profile 100%. And the intend is to select two co-chairs that can complement each other and work together. As for the profile: - Good management and process skills, including but not limited to choosing and supervising editors, commitment and followthrough on the charter, active management of the working group discussions, and handling IETF process steps in prompt fashion. - Good basic knowledge of the AAA protocols. That not only includes Diameter, but also Radius. - Understanding of the requirements/needs/applications of AAA protocols. Specifically, understanding the needs of other organizations (like 3GPP) is a useful asset. - Operational background/experience is very desirable. - Enough available time. For example, preferable not more than one other working chair role in IETF. - There is no requirement that the candidate has been an IETF working group chair before, but it helps if there is some evidence that the candidate can fullfill such a role (eg. other management role in other places than IETF etc.) We would like to receive your comments & nominations by Jan 30th 2006 and we plan to make a decision as soon as possible thereafter. It will be helpful if you indicate in your nomination mail how you or the nominated candidate fits this profile as best as possible. And last but not least, we would like to thank John Loughney for leading/guiding the work to develop the DIME WG charter. He also started a new mailing list: dime@ietf.org David Kessens & Bert Wijnen +++ Diameter Maintenance and Extensions (dime) =========================================== Current Status: Proposed Working Group WG Chair(s): TBD Operations and Management Area Director(s): Bert Wijnen David Kessens Operations and Management Area Advisor: Bert Wijnen Description of Working Group: The Diameter Maintanence and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use in applications such as IP telephony and Local Area Network authentication, authorization and accounting. The IETF has recently completed work on the Diameter Base protocol. There is on-going work on defining RADIUS extensions. The work done in the DiME WG will ensure that work done in RADext is also available for Diameter. The immediate goals of the DiME working group are to address the following issues: - Maintaining and/or progressing, along the standards track, the Diameter procotol and Diameter Applications. Every revised document to be "maintained" requires explicit approval before it will be accepted as a WG document. - An informational RFC on a Diameter API. - Diameter Application design guidelines. This document will provide guidelines for design of new Diameter Applications. It will detail when to consider reusing an existing application and when to develop a new application. Interaction between vendor & SDO specific extensions and applications will be covered. - Diameter QoS application. This document will develop a new Diameter application for supporting QoS in AAA deployments. The NSIS WG will be consulted on proper design of QoS attributes. - Diameter URI. RFC 3588 defines an AAA URI which has some know problems. A document revising the AAA URI as a specific Diameter URI will be developed. - Diameter extensions for MIPv6. This may include support for Mobile IP extensions, like FMIP; as well as support for MIP bootstrapping. Additionally, AAA systems require interoperability in order to work. Uncontrolled extensibility is not a mechanism for interoperability. Therefore, the working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed. Coordination with other IETF working groups and other SDOs will used to ensure this. Drafts http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-api-04.txt http://www.ietf.org/internet-drafts/draft-alfano-aaa-qosprot-03.txt http://tools.ietf.org/wg/aaa/draft-ietf-aaa-uri/draft-ietf-aaa-uri-01.txt http://www.tschofenig.priv.at/drafts/draft-tschofenig-mip6-aaa-ha-diameter-00.txt http://www.watersprings.org/pub/id/draft-le-aaa-diameter-mobileipv6-04.txt Milestones Mar 06 Submit Diameter API to IESG as an information RFC. May 06 Submit Diameter URI to IESG as an information RFC. Sep 06 Submit Diameter QoS Application to IESG as a Proposed Standard. Sep 06 Submit Diameter Application Design Guidelines to IESG as an informational RFC. Jan 07 Submit Diameter Base to IESG as a Draft Standard _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 06:42:31 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1j2l-0007SE-KB; Wed, 25 Jan 2006 06:42:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1j2j-0007Rt-Ex for dime@megatron.ietf.org; Wed, 25 Jan 2006 06:42:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03359 for ; Wed, 25 Jan 2006 06:40:58 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1jCS-00057T-F9 for dime@ietf.org; Wed, 25 Jan 2006 06:52:33 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0PBdAMS019413; Wed, 25 Jan 2006 13:39:10 +0200 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jan 2006 13:41:43 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jan 2006 13:41:43 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jan 2006 13:41:41 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D019AB34E@esebe100.NOE.Nokia.com> Thread-Topic: Diameter interop update Thread-Index: AcYhmE+naqhQX2MRRWO125XjdqPz2QACn2PQ To: X-OriginalArrivalTime: 25 Jan 2006 11:41:43.0273 (UTC) FILETIME=[5054DD90:01C621A4] X-Spam-Score: 0.3 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: quoted-printable Subject: [Dime] Diameter interop update X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org (BCC:ed to RADext, AAA mailing lists and a few indivituals). Hi all, I've gotten a large number of responses - about 18 - for an interop, so it looks like it's a go! Ulticom is happy to sponser the interop event, in Mt. Laurel, NJ - which is close to Philadelphia. The current plan is to hold the event starting on Monday April 24th. This is due to the availability of the testing facilities. If this week is a problem for some of you, please let me know immediately. I'm working with Ulticom on setting up a registration page, so they can figure out how much space is needed. Protocols that people have shown interest are: Diameter Base =09 Diameter Credit Control=09 Diameter SIP =09 3GPP interfaces (Cx)=09 Diameter EAP =09 Diameter NASREQ =09 Diameter MIP =09 What is needed is a test plan, test cases. A couple of you indicated that you'd be interested in preparing this, so I think the best way to do this would be do document them in an Internet Draft and submit them before the draft cut-off date. As I guide, I'm looking at these pages, from a past interop event: http://standards.ericsson.net/diameter-bake-off/ I'd strongly suggest that all interested parties subscribe to the Diameter Maintanence and Extentions WG mailing list, for discussions. thanks, John _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 06:44:39 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1j4p-0007z8-0W; Wed, 25 Jan 2006 06:44:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1j4m-0007yT-KK; Wed, 25 Jan 2006 06:44:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03469; Wed, 25 Jan 2006 06:43:06 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1jEU-0005Bj-Bj; Wed, 25 Jan 2006 06:54:40 -0500 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0PBiSiT024665; Wed, 25 Jan 2006 13:44:28 +0200 Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jan 2006 13:44:25 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jan 2006 13:44:25 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jan 2006 13:44:24 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D019AB352@esebe100.NOE.Nokia.com> Thread-Topic: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 Thread-Index: AcYaC85mJCwfhNw9TCa7JEZv72INhgG/AmUAACcmacA= To: , X-OriginalArrivalTime: 25 Jan 2006 11:44:25.0573 (UTC) FILETIME=[B111E150:01C621A4] X-Spam-Score: 0.4 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Content-Transfer-Encoding: quoted-printable Cc: falfano@lucent.com, mccap@lucent.com, dime@ietf.org, tseno.tsenov@gmail.com Subject: [Dime] RE: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi all, Its fine to discuss some QoS issues for this draft, but since this is a potential work item for the DiME (Diameter Maintanence and Extentions) Working Group, perhaps it would be good to have some discussions there. DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime=20 thanks, John PS - I BCC:ed the NSIS mailing list, to avoid cross-posted replies. >-----Original Message----- >From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20 >Behalf Of ext Hancock, Robert >Sent: 24 January, 2006 19:30 >To: Tschofenig, Hannes >Cc: falfano@lucent.com; mccap@lucent.com; Tseno Tsenov; nsis@ietf.org >Subject: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 > >hi all, > >i haven't re-read the full draft, but checked the issues below. > >> -----Original Message----- >> From: Tschofenig, Hannes [mailto:hannes.tschofenig@siemens.com] >> Sent: 15 January 2006 21:29 >> To: Hancock, Robert >> Cc: mccap@lucent.com; falfano@lucent.com; Tseno Tsenov; nsis@ietf.org >> Subject: Diameter QoS Draft: Issue #16, #20, #22 >>=20 >>=20 >> Hi Robert, >>=20 >> you provided feedback for the Diameter QoS application draft.=20 >> We would like to close the open issues based on the draft=20 >version -05: >> http://tools.ietf.org/wg/aaa/draft-alfano-aaa-qosprot-05.txt >>=20 >> We created the following issues after your review. We updated the=20 >> draft based on your feedback and reflected your comment. >>=20 >> Two party authorization model >> http://www.tschofenig.priv.at:8080/diameter-qos/issue16 > >in 3.2 the final part of the first paragraph reads: > "With the 'Two party model' the QoS resource requesting > entity is authenticated by the Network Element and the authorization > decision is made either locally at the Network Element itself or > offloaded to a trusted entity (most likely within the same > administrative domain). In the former case no Diameter QoS protocol > interaction is required." > >which i parse as > >"In the two party model, the requesting entity is=20 >authenticated by the NE and there are two cases >former) authorization decision is made locally at the Network=20 > Element itself >latter) the authorization decision is offloaded to a trusted=20 > entity (most likely within the same administrative=20 >domain) In the former case no Diameter QoS protocol=20 >interaction is required." > >So ... is the Diameter QoS protocol interaction required in the >*latter* case? Is it in the scope of this document? (And why=20 >the expectation that such an interaction would not cross a domain >boundary?) Or is the entire scenario out of scope? > >>=20 >> Suggestion:Close >>=20 >> Gating >> http://www.tschofenig.priv.at:8080/diameter-qos/issue20 > >i think what is still needed (what i was originally confused >about) is a clarification that 'disabled' really means=20 >'packets are blocked' (if this is what you mean). the origin=20 >of my confusion is that I assumed that the document is about=20 >authorising reservations in a network environment where the=20 >default is 'best efforts', whereas the gating discussion seems=20 >to imply an environment where the default is 'blocked'. > >>=20 >> Suggestion:Close >>=20 >> Session Identifier=20 >http://www.tschofenig.priv.at:8080/diameter-qos/issue22 > >i think i understand the proposal, but the ABNF is quite confusing. >AFAICT the QoS-Auth-Resources AVP can optionally=20 >(syntactically) have a Signaling-Session-ID AVP and a Flows=20 >AVP, and the Flows AVP can have a set of IND-Flows AVPs each=20 >of which can have any/all of a Flow-Id, QoS-Filter-Rule and=20 >SPI. would it be possible to structure things so that the fact=20 >that Signaling-Session-ID, Flow-ID and the combination of=20 >{QoSFilter-Rule with SPI} were alternatives? (i.e. A|B|C format)? >or is it not that simple? > >>=20 >> Suggestion:Close >>=20 >> Ciao >> Hannes >>=20 > >_______________________________________________ >nsis mailing list >nsis@ietf.org >https://www1.ietf.org/mailman/listinfo/nsis > _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 08:54:50 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1l6o-0002DJ-8E; Wed, 25 Jan 2006 08:54:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1l6j-0002Cz-HD for dime@megatron.ietf.org; Wed, 25 Jan 2006 08:54:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13693 for ; Wed, 25 Jan 2006 08:53:12 -0500 (EST) Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1lGR-0001h1-Fv for dime@ietf.org; Wed, 25 Jan 2006 09:04:49 -0500 Received: from mail1.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id k0PDsN7X025034; Wed, 25 Jan 2006 14:54:23 +0100 Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net [157.163.133.201]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id k0PDsNJW029941; Wed, 25 Jan 2006 14:54:23 +0100 Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jan 2006 14:54:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Jan 2006 14:53:36 +0100 Message-ID: Thread-Topic: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 Thread-Index: AcYaC85mJCwfhNw9TCa7JEZv72INhgG/AmUAACcmacAABIlvIA== From: "Tschofenig, Hannes" To: , X-OriginalArrivalTime: 25 Jan 2006 13:54:21.0428 (UTC) FILETIME=[D7C2F340:01C621B6] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Content-Transfer-Encoding: quoted-printable Cc: falfano@lucent.com, mccap@lucent.com, dime@ietf.org, tseno.tsenov@gmail.com Subject: [Dime] AW: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org hi john,=20 you are certainly right. sorry for initiating these discussions on the = nsis list only.=20 we should move them all to the recently created dime list.=20 ciao hannes=20 > -----Urspr=FCngliche Nachricht----- > Von: john.loughney@nokia.com [mailto:john.loughney@nokia.com]=20 > Gesendet: Mittwoch, 25. Januar 2006 12:44 > An: robert.hancock@roke.co.uk; Tschofenig, Hannes > Cc: falfano@lucent.com; mccap@lucent.com;=20 > tseno.tsenov@gmail.com; dime@ietf.org > Betreff: RE: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 >=20 > Hi all, >=20 > Its fine to discuss some QoS issues for this draft, but since=20 > this is a > potential work item for the DiME (Diameter Maintanence and Extentions) > Working Group, perhaps it would be good to have some=20 > discussions there. >=20 > DiME@ietf.org > https://www1.ietf.org/mailman/listinfo/dime=20 >=20 > thanks, > John >=20 > PS - I BCC:ed the NSIS mailing list, to avoid cross-posted replies. >=20 > >-----Original Message----- > >From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20 > >Behalf Of ext Hancock, Robert > >Sent: 24 January, 2006 19:30 > >To: Tschofenig, Hannes > >Cc: falfano@lucent.com; mccap@lucent.com; Tseno Tsenov; nsis@ietf.org > >Subject: [NSIS] RE: Diameter QoS Draft: Issue #16, #20, #22 > > > >hi all, > > > >i haven't re-read the full draft, but checked the issues below. > > > >> -----Original Message----- > >> From: Tschofenig, Hannes [mailto:hannes.tschofenig@siemens.com] > >> Sent: 15 January 2006 21:29 > >> To: Hancock, Robert > >> Cc: mccap@lucent.com; falfano@lucent.com; Tseno Tsenov;=20 > nsis@ietf.org > >> Subject: Diameter QoS Draft: Issue #16, #20, #22 > >>=20 > >>=20 > >> Hi Robert, > >>=20 > >> you provided feedback for the Diameter QoS application draft.=20 > >> We would like to close the open issues based on the draft=20 > >version -05: > >> http://tools.ietf.org/wg/aaa/draft-alfano-aaa-qosprot-05.txt > >>=20 > >> We created the following issues after your review. We updated the=20 > >> draft based on your feedback and reflected your comment. > >>=20 > >> Two party authorization model > >> http://www.tschofenig.priv.at:8080/diameter-qos/issue16 > > > >in 3.2 the final part of the first paragraph reads: > > "With the 'Two party model' the QoS resource requesting > > entity is authenticated by the Network Element and the=20 > authorization > > decision is made either locally at the Network Element itself or > > offloaded to a trusted entity (most likely within the same > > administrative domain). In the former case no Diameter=20 > QoS protocol > > interaction is required." > > > >which i parse as > > > >"In the two party model, the requesting entity is=20 > >authenticated by the NE and there are two cases > >former) authorization decision is made locally at the Network=20 > > Element itself > >latter) the authorization decision is offloaded to a trusted=20 > > entity (most likely within the same administrative=20 > >domain) In the former case no Diameter QoS protocol=20 > >interaction is required." > > > >So ... is the Diameter QoS protocol interaction required in the > >*latter* case? Is it in the scope of this document? (And why=20 > >the expectation that such an interaction would not cross a domain > >boundary?) Or is the entire scenario out of scope? > > > >>=20 > >> Suggestion:Close > >>=20 > >> Gating > >> http://www.tschofenig.priv.at:8080/diameter-qos/issue20 > > > >i think what is still needed (what i was originally confused > >about) is a clarification that 'disabled' really means=20 > >'packets are blocked' (if this is what you mean). the origin=20 > >of my confusion is that I assumed that the document is about=20 > >authorising reservations in a network environment where the=20 > >default is 'best efforts', whereas the gating discussion seems=20 > >to imply an environment where the default is 'blocked'. > > > >>=20 > >> Suggestion:Close > >>=20 > >> Session Identifier=20 > >http://www.tschofenig.priv.at:8080/diameter-qos/issue22 > > > >i think i understand the proposal, but the ABNF is quite confusing. > >AFAICT the QoS-Auth-Resources AVP can optionally=20 > >(syntactically) have a Signaling-Session-ID AVP and a Flows=20 > >AVP, and the Flows AVP can have a set of IND-Flows AVPs each=20 > >of which can have any/all of a Flow-Id, QoS-Filter-Rule and=20 > >SPI. would it be possible to structure things so that the fact=20 > >that Signaling-Session-ID, Flow-ID and the combination of=20 > >{QoSFilter-Rule with SPI} were alternatives? (i.e. A|B|C format)? > >or is it not that simple? > > > >>=20 > >> Suggestion:Close > >>=20 > >> Ciao > >> Hannes > >>=20 > > > >_______________________________________________ > >nsis mailing list > >nsis@ietf.org > >https://www1.ietf.org/mailman/listinfo/nsis > > >=20 _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 11:18:30 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1nLp-0001rn-Sc; Wed, 25 Jan 2006 11:18:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1nLo-0001qt-GQ for dime@megatron.ietf.org; Wed, 25 Jan 2006 11:18:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25190 for ; Wed, 25 Jan 2006 11:16:55 -0500 (EST) Received: from mgw.toshibaamericaresearch.com ([165.254.55.12] helo=toshi17.tari.toshiba.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1nVZ-0006a8-4N for dime@ietf.org; Wed, 25 Jan 2006 11:28:34 -0500 Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id k0PGI6pM057407; Wed, 25 Jan 2006 11:18:07 -0500 (EST) (envelope-from vfajardo@tari.toshiba.com) Message-ID: <43D7A4BF.7030105@tari.toshiba.com> Date: Wed, 25 Jan 2006 11:18:07 -0500 From: Victor Fajardo User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: john.loughney@nokia.com Subject: Re: [Dime] Diameter interop update References: <1AA39B75171A7144A73216AED1D7478D019AB34E@esebe100.NOE.Nokia.com> In-Reply-To: <1AA39B75171A7144A73216AED1D7478D019AB34E@esebe100.NOE.Nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: 7bit Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi all, The open diameter project is interested in starting/contributing a draft document for test plan and test case. At the moment, we would like to gather feedback from folks who would also be interested in collaborating so we can bootstrap this process. The initial scope is based on John's protocol list below. We can discuss further details for each item as we proceed. thanks, Victor Fajardo >(BCC:ed to RADext, AAA mailing lists and a few indivituals). > >Hi all, > >I've gotten a large number of responses - about 18 - for an interop, so >it looks like it's a go! > >Ulticom is happy to sponser the interop event, in Mt. Laurel, NJ - which >is close to Philadelphia. The current plan is to hold the event >starting on Monday April 24th. This is due to the availability of the >testing facilities. If this week is a problem for some of you, please >let me know immediately. I'm working with Ulticom on setting up a >registration page, so they can figure out how much space is needed. > >Protocols that people have shown interest are: > > Diameter Base > Diameter Credit Control > Diameter SIP > 3GPP interfaces (Cx) > Diameter EAP > Diameter NASREQ > Diameter MIP > >What is needed is a test plan, test cases. A couple of you indicated >that you'd be interested in preparing this, so I think the best way to >do this would be do document them in an Internet Draft and submit them >before the draft cut-off date. As I guide, I'm looking at these pages, >from a past interop event: >http://standards.ericsson.net/diameter-bake-off/ > >I'd strongly suggest that all interested parties subscribe to the >Diameter Maintanence and Extentions WG mailing list, for discussions. > >thanks, >John > >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www1.ietf.org/mailman/listinfo/dime > > > > > _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 18:45:03 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1uJy-0001If-SS; Wed, 25 Jan 2006 18:45:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1uJx-0001IF-QC for dime@megatron.ietf.org; Wed, 25 Jan 2006 18:45:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04954 for ; Wed, 25 Jan 2006 18:43:29 -0500 (EST) Received: from smtp2.int-evry.fr ([157.159.10.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1uTl-0006pf-QM for dime@ietf.org; Wed, 25 Jan 2006 18:55:11 -0500 Received: from smyrne.int-evry.fr (smtp-ext.int-evry.fr [157.159.11.17]) by smtp2.int-evry.fr (Postfix) with ESMTP id A00DB80BC; Thu, 26 Jan 2006 00:44:43 +0100 (CET) Received: from [192.168.0.109] (ppp210.39.marunouchi.tokyo.dcn.ne.jp [219.105.39.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smyrne.int-evry.fr (Postfix) with ESMTP id 18048FF065; Thu, 26 Jan 2006 00:42:41 +0100 (CET) Message-ID: <43D87D43.3070100@int-evry.fr> Date: Thu, 26 Jan 2006 08:41:55 +0100 From: Julien Bournelle User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Victor Fajardo Subject: Re: [Dime] Diameter interop update References: <1AA39B75171A7144A73216AED1D7478D019AB34E@esebe100.NOE.Nokia.com> <43D7A4BF.7030105@tari.toshiba.com> In-Reply-To: <43D7A4BF.7030105@tari.toshiba.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-INT-MailScanner-Information: Please contact the ISP for more information X-INT-MailScanner: Found to be clean X-MailScanner-From: julien.bournelle@int-evry.fr X-Spam-Score: 1.9 (+) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 7bit Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi all, Victor Fajardo wrote: > Hi all, > > The open diameter project is interested in starting/contributing a draft > document for test plan and test case. I can help if needed (at least for Diameter Base Protocol and Diameter EAP). Julien > At the moment, we would like to > gather feedback from folks who would also be interested in collaborating > so we can bootstrap this process. The initial scope is based on John's > protocol list below. We can discuss further details for each item as we > proceed. > > thanks, > Victor Fajardo > >> (BCC:ed to RADext, AAA mailing lists and a few indivituals). >> >> Hi all, >> >> I've gotten a large number of responses - about 18 - for an interop, so >> it looks like it's a go! >> >> Ulticom is happy to sponser the interop event, in Mt. Laurel, NJ - which >> is close to Philadelphia. The current plan is to hold the event >> starting on Monday April 24th. This is due to the availability of the >> testing facilities. If this week is a problem for some of you, please >> let me know immediately. I'm working with Ulticom on setting up a >> registration page, so they can figure out how much space is needed. >> >> Protocols that people have shown interest are: >> >> Diameter Base >> Diameter Credit Control >> Diameter SIP >> 3GPP interfaces (Cx) >> Diameter EAP >> Diameter NASREQ >> Diameter MIP >> >> What is needed is a test plan, test cases. A couple of you indicated >> that you'd be interested in preparing this, so I think the best way to >> do this would be do document them in an Internet Draft and submit them >> before the draft cut-off date. As I guide, I'm looking at these pages, >> from a past interop event: >> http://standards.ericsson.net/diameter-bake-off/ >> >> I'd strongly suggest that all interested parties subscribe to the >> Diameter Maintanence and Extentions WG mailing list, for discussions. >> >> thanks, >> John >> >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www1.ietf.org/mailman/listinfo/dime >> >> >> >> >> > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www1.ietf.org/mailman/listinfo/dime _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Wed Jan 25 21:36:53 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1x0H-0007Rw-9D; Wed, 25 Jan 2006 21:36:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1x0F-0007Ro-5J for dime@megatron.ietf.org; Wed, 25 Jan 2006 21:36:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29666 for ; Wed, 25 Jan 2006 21:35:17 -0500 (EST) Received: from mgw.toshibaamericaresearch.com ([165.254.55.12] helo=toshi17.tari.toshiba.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1xA4-0008Se-6d for dime@ietf.org; Wed, 25 Jan 2006 21:47:01 -0500 Received: from [127.0.0.1] (mgw.toshibaamericaresearch.com [165.254.55.12]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id k0Q2aZfA060271; Wed, 25 Jan 2006 21:36:35 -0500 (EST) (envelope-from vfajardo@tari.toshiba.com) Message-ID: <43D835B4.2030402@tari.toshiba.com> Date: Wed, 25 Jan 2006 21:36:36 -0500 From: Victor Fajardo User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julien Bournelle Subject: Re: [Dime] Diameter interop update References: <1AA39B75171A7144A73216AED1D7478D019AB34E@esebe100.NOE.Nokia.com> <43D7A4BF.7030105@tari.toshiba.com> <43D87D43.3070100@int-evry.fr> In-Reply-To: <43D87D43.3070100@int-evry.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7bit Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi Julien, > Hi all, > > > Victor Fajardo wrote: > >> Hi all, >> >> The open diameter project is interested in starting/contributing a >> draft document for test plan and test case. > > > I can help if needed (at least for Diameter Base Protocol and > Diameter EAP). Thanks. I'm hoping other people with expertise in the other protocols will also be able to contribute. Anyway, we can take the detailed discussion offline for now until we have an initial version of the document. If others wish to contribute, pls feel free to contact us. Victor Fajardo _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Thu Jan 26 08:05:30 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F26oc-0000cd-Il; Thu, 26 Jan 2006 08:05:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F24Wq-0000dN-4M for dime@megatron.ietf.org; Thu, 26 Jan 2006 05:39:05 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02187 for ; Thu, 26 Jan 2006 05:37:27 -0500 (EST) Received: from mail.openet-telecom.com ([62.17.151.60] helo=mimesweeper.openet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F24gk-0006ho-Vz for dime@ietf.org; Thu, 26 Jan 2006 05:49:16 -0500 Received: from exc03.openet-telecom.lan (exc03.openet-telecom.com) by mimesweeper.openet.com (Clearswift SMTPRS 5.0.9) with ESMTP id ; Thu, 26 Jan 2006 10:38:47 +0000 Content-class: urn:content-classes:message Subject: RE: [Dime] Diameter interop update MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 26 Jan 2006 10:38:47 -0000 x-mimeole: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: <8276FAA6D84AA54987B825CD51EDFAA601E1AC3B@exc03.openet-dublin> Thread-Topic: [Dime] Diameter interop update Thread-Index: AcYiIaV1fHiMf7ipT/+yPWqA6Kp0mgAQLhPg From: "Alan McNamee" To: "Victor Fajardo" , "Julien Bournelle" X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 26 Jan 2006 08:05:28 -0500 Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi, I am happy on behalf of Openet Telecom to contribute to a test plan for the Diameter CCA interop. We have performed a number of Diameter CCA interops in the past which I could draw upon to come with a draft test plan. We could also contribute tests for Diameter base protocol accounting if there is interest in doing so (and possibly extend to 3GPP offline IMS charging).=20 Regards, Alan. -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Victor Fajardo Sent: 26 January 2006 02:37 To: Julien Bournelle Cc: dime@ietf.org Subject: Re: [Dime] Diameter interop update Hi Julien, > Hi all, > > > Victor Fajardo wrote: > >> Hi all, >> >> The open diameter project is interested in starting/contributing a=20 >> draft document for test plan and test case. > > > I can help if needed (at least for Diameter Base Protocol and=20 > Diameter EAP). Thanks. I'm hoping other people with expertise in the other protocols will also be able to contribute. Anyway, we can take the detailed discussion offline for now until we have an initial version of the document. If others wish to contribute, pls feel free to contact us. Victor Fajardo _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Thu Jan 26 08:16:35 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F26vS-0003x0-E3; Thu, 26 Jan 2006 08:12:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F26vL-0003vV-E3 for dime@megatron.ietf.org; Thu, 26 Jan 2006 08:12:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12402 for ; Thu, 26 Jan 2006 08:10:55 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F275F-00035p-Qc for dime@ietf.org; Thu, 26 Jan 2006 08:22:45 -0500 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0QD9aaV010478; Thu, 26 Jan 2006 15:09:40 +0200 Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jan 2006 15:12:16 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jan 2006 15:12:15 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Dime] Diameter interop update Date: Thu, 26 Jan 2006 15:12:14 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D019AB6F8@esebe100.NOE.Nokia.com> Thread-Topic: [Dime] Diameter interop update Thread-Index: AcYiIaV1fHiMf7ipT/+yPWqA6Kp0mgAQLhPgAAXKsCA= To: , , X-OriginalArrivalTime: 26 Jan 2006 13:12:15.0425 (UTC) FILETIME=[208F3B10:01C6227A] X-Spam-Score: 0.3 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Content-Transfer-Encoding: quoted-printable Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi all, What I would suggest is that you guys start writing drafts, and we can discuss them on the mailing list. I'd like to have discussion about the test plans at the next IETF meeting in Dallas. Just to remind you, February 27, Monday is the Internet Draft Cut-off for initial document=20 (-00) submission by 09:00 ET (14:00 GMT). John >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On=20 >Behalf Of ext Alan McNamee >Sent: 26 January, 2006 12:39 >To: Victor Fajardo; Julien Bournelle >Cc: dime@ietf.org >Subject: RE: [Dime] Diameter interop update > >Hi, > >I am happy on behalf of Openet Telecom to contribute to a test=20 >plan for the Diameter CCA interop. We have performed a number=20 >of Diameter CCA interops in the past which I could draw upon=20 >to come with a draft test plan. > >We could also contribute tests for Diameter base protocol=20 >accounting if there is interest in doing so (and possibly=20 >extend to 3GPP offline IMS charging).=20 > >Regards, > >Alan. > >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On=20 >Behalf Of Victor Fajardo >Sent: 26 January 2006 02:37 >To: Julien Bournelle >Cc: dime@ietf.org >Subject: Re: [Dime] Diameter interop update > >Hi Julien, > >> Hi all, >> >> >> Victor Fajardo wrote: >> >>> Hi all, >>> >>> The open diameter project is interested in starting/contributing a=20 >>> draft document for test plan and test case. >> >> >> I can help if needed (at least for Diameter Base Protocol and=20 >> Diameter EAP). > >Thanks. I'm hoping other people with expertise in the other=20 >protocols will also be able to contribute. Anyway, we can take=20 >the detailed discussion offline for now until we have an=20 >initial version of the document. If others wish to contribute,=20 >pls feel free to contact us. > >Victor Fajardo > > >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www1.ietf.org/mailman/listinfo/dime > >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www1.ietf.org/mailman/listinfo/dime > _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Thu Jan 26 09:55:40 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F28XE-0007gS-Lj; Thu, 26 Jan 2006 09:55:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F28XC-0007ef-L6 for dime@megatron.ietf.org; Thu, 26 Jan 2006 09:55:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22411 for ; Thu, 26 Jan 2006 09:54:04 -0500 (EST) Received: from mgw.toshibaamericaresearch.com ([165.254.55.12] helo=toshi17.tari.toshiba.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F28h7-0007MP-RQ for dime@ietf.org; Thu, 26 Jan 2006 10:05:55 -0500 Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id k0QEtO3F061751; Thu, 26 Jan 2006 09:55:24 -0500 (EST) (envelope-from vfajardo@tari.toshiba.com) Message-ID: <43D8E2DD.4050502@tari.toshiba.com> Date: Thu, 26 Jan 2006 09:55:25 -0500 From: Victor Fajardo User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan McNamee Subject: Re: [Dime] Diameter interop update References: <8276FAA6D84AA54987B825CD51EDFAA601E1AC3B@exc03.openet-dublin> In-Reply-To: <8276FAA6D84AA54987B825CD51EDFAA601E1AC3B@exc03.openet-dublin> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit Cc: dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi Alan, >Hi, > >I am happy on behalf of Openet Telecom to contribute to a test plan for >the Diameter CCA interop. We have performed a number of Diameter CCA >interops in the past which I could draw upon to come with a draft test >plan. > > Thanks. Your experience is really useful. I'm hoping we can come up with an initial version soon (soon = 1 week ?) with skeleton contents on areas we lack expertise on. From there we can solicit more contributions. Anyway, we can continue offline with the details. >We could also contribute tests for Diameter base protocol accounting if >there is interest in doing so (and possibly extend to 3GPP offline IMS >charging). > > I think we should include test cases for 3GPP/IMS. A broad scope for the document is more helpful to the community in general since this is a metric of an implementations functionality. Though the level and granularity of the test details for each area needs to be worked on. Victor Fajardo _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Thu Jan 26 10:03:48 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F28f6-0003C5-Jw; Thu, 26 Jan 2006 10:03:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F28f4-0003BW-LV for dime@megatron.ietf.org; Thu, 26 Jan 2006 10:03:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23252 for ; Thu, 26 Jan 2006 10:02:14 -0500 (EST) Received: from mgw.toshibaamericaresearch.com ([165.254.55.12] helo=toshi17.tari.toshiba.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F28p1-0007ht-Un for dime@ietf.org; Thu, 26 Jan 2006 10:14:05 -0500 Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id k0QF3gaJ061777; Thu, 26 Jan 2006 10:03:42 -0500 (EST) (envelope-from vfajardo@tari.toshiba.com) Message-ID: <43D8E4CF.7050607@tari.toshiba.com> Date: Thu, 26 Jan 2006 10:03:43 -0500 From: Victor Fajardo User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: john.loughney@nokia.com Subject: Re: [Dime] Diameter interop update References: <1AA39B75171A7144A73216AED1D7478D019AB6F8@esebe100.NOE.Nokia.com> In-Reply-To: <1AA39B75171A7144A73216AED1D7478D019AB6F8@esebe100.NOE.Nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Content-Transfer-Encoding: 7bit Cc: Alan.McNamee@openet-telecom.com, dime@ietf.org X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org Hi John, >Hi all, > >What I would suggest is that you guys start writing drafts, and we can >discuss them on >the mailing list. I'd like to have discussion about the test plans at >the next IETF >meeting in Dallas. > > I agree. Victor >Just to remind you, February 27, Monday is the Internet Draft Cut-off >for initial document >(-00) submission by 09:00 ET (14:00 GMT). > >John > > > >>-----Original Message----- >>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >>Behalf Of ext Alan McNamee >>Sent: 26 January, 2006 12:39 >>To: Victor Fajardo; Julien Bournelle >>Cc: dime@ietf.org >>Subject: RE: [Dime] Diameter interop update >> >>Hi, >> >>I am happy on behalf of Openet Telecom to contribute to a test >>plan for the Diameter CCA interop. We have performed a number >>of Diameter CCA interops in the past which I could draw upon >>to come with a draft test plan. >> >>We could also contribute tests for Diameter base protocol >>accounting if there is interest in doing so (and possibly >>extend to 3GPP offline IMS charging). >> >>Regards, >> >>Alan. >> >>-----Original Message----- >>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >>Behalf Of Victor Fajardo >>Sent: 26 January 2006 02:37 >>To: Julien Bournelle >>Cc: dime@ietf.org >>Subject: Re: [Dime] Diameter interop update >> >>Hi Julien, >> >> >> >>>Hi all, >>> >>> >>>Victor Fajardo wrote: >>> >>> >>> >>>>Hi all, >>>> >>>>The open diameter project is interested in starting/contributing a >>>>draft document for test plan and test case. >>>> >>>> >>> I can help if needed (at least for Diameter Base Protocol and >>>Diameter EAP). >>> >>> >>Thanks. I'm hoping other people with expertise in the other >>protocols will also be able to contribute. Anyway, we can take >>the detailed discussion offline for now until we have an >>initial version of the document. If others wish to contribute, >>pls feel free to contact us. >> >>Victor Fajardo >> >> >>_______________________________________________ >>DiME mailing list >>DiME@ietf.org >>https://www1.ietf.org/mailman/listinfo/dime >> >>_______________________________________________ >>DiME mailing list >>DiME@ietf.org >>https://www1.ietf.org/mailman/listinfo/dime >> >> >> > > > > > _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Tue Jan 31 03:55:52 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3rIl-0000b3-Pj; Tue, 31 Jan 2006 03:55:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3rIj-0000aL-Jd for dime@megatron.ietf.org; Tue, 31 Jan 2006 03:55:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26297 for ; Tue, 31 Jan 2006 03:54:12 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3rTd-0002cq-IU for dime@ietf.org; Tue, 31 Jan 2006 04:07:07 -0500 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0V8oecq024625; Tue, 31 Jan 2006 10:50:41 +0200 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jan 2006 10:55:40 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jan 2006 10:55:38 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 31 Jan 2006 10:55:37 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D019AC07E@esebe100.NOE.Nokia.com> Thread-Topic: [Mip6] New version of AAA-HA Goals draft Thread-Index: AcYk91DNzIIkEcJoRmOV0PSn//i38gBTLIZA To: X-OriginalArrivalTime: 31 Jan 2006 08:55:38.0335 (UTC) FILETIME=[1B3E7EF0:01C62644] X-Spam-Score: 0.4 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable Cc: Gerardo.Giaretta@TILAB.COM Subject: [Dime] RE: [Mip6] New version of AAA-HA Goals draft X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org This document is being discussed on the MIPv6 mailing list. We might be interested in this. John >-----Original Message----- >From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20 >Behalf Of ext Gerardo Giaretta >Sent: 29 January, 2006 19:14 >To: mip6@ietf.org >Subject: [Mip6] New version of AAA-HA Goals draft > >Hi all, > >a new version of the AAA-HA Goals draft is available at=20 >http://www.ietf.org/internet-drafts/draft-ietf-mip6-aaa-ha-goals-01.txt . >The draft has been updated based on the bootstrapping=20 >solutions defined by the Bootstrapping Design Team.=20 > >Please provide your comments and feedback. > >Regards, >--Gerardo _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime From dime-bounces@ietf.org Tue Jan 31 04:22:40 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3rii-00086f-1q; Tue, 31 Jan 2006 04:22:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3rig-00083g-3t; Tue, 31 Jan 2006 04:22:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28184; Tue, 31 Jan 2006 04:20:54 -0500 (EST) From: john.loughney@nokia.com Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3rtT-0003WU-To; Tue, 31 Jan 2006 04:33:49 -0500 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0V9HPaq024256; Tue, 31 Jan 2006 11:17:25 +0200 Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jan 2006 11:22:18 +0200 Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jan 2006 11:22:17 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 31 Jan 2006 11:22:16 +0200 Message-ID: <1AA39B75171A7144A73216AED1D7478D019AC0C6@esebe100.NOE.Nokia.com> Thread-Topic: Internet-Drafts Submission Cutoff Dates for the 65th IETF Meeting in Dallas, TX, USA Thread-Index: AcYi/6AMDxDEqhsjSJGvbaIAr/D0NgDSCjCg To: , X-OriginalArrivalTime: 31 Jan 2006 09:22:17.0794 (UTC) FILETIME=[D4989220:01C62647] X-Spam-Score: 0.4 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: quoted-printable Cc: Subject: [Dime] FW: Internet-Drafts Submission Cutoff Dates for the 65th IETF Meeting in Dallas, TX, USA X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dime-bounces@ietf.org Errors-To: dime-bounces@ietf.org >There are two (2) Internet-Draft cutoff dates for the 65th=20 >IETF Meeting in Dallas, TX, USA: > >February 27th: Cutoff Date for Initial (i.e., version -00)=20 >Internet-Draft Submissions=20 > >All initial Internet-Drafts (version -00) must be submitted by=20 >Monday, February 27th at 9:00 AM ET. As always, all initial=20 >submissions with a filename beginning with "draft-ietf" must=20 >be approved by the appropriate WG Chair before they can be=20 >processed or announced. The Secretariat would appreciate=20 >receiving WG Chair approval by Monday, February 20th at 9:00 AM ET. > >March 6th: Cutoff Date for Revised (i.e., version -01 and=20 >higher) Internet-Draft Submissions=20 > >All revised Internet-Drafts (version -01 and higher) must be=20 >submitted by Monday, March 6th at 9:00 AM ET. > >Initial and revised Internet-Drafts received after their=20 >respective cutoff dates will not be made available in the=20 >Internet-Drafts directory or announced until on or after=20 >Monday, March 20th at 9:00 AM ET, when Internet-Draft posting=20 >resumes. Please do not wait until the last minute to submit. > >Thank you for your understanding and cooperation. If you have=20 >any questions or concerns, then please send a message to=20 >internet-drafts@ietf.org. > >The IETF Secretariat > >FYI: The Internet-Draft cutoff dates as well as other=20 >significant dates for the 65th IETF Meeting can be found at=20 >http://www.ietf.org/meetings/cutoff_dates_65.html. _______________________________________________ DiME mailing list DiME@ietf.org https://www1.ietf.org/mailman/listinfo/dime