Re: [Dime] FW: DIME Milestones Update

Tina TSOU <tena@huawei.com> Wed, 24 December 2008 09:30 UTC

Return-Path: <dime-bounces@ietf.org>
X-Original-To: dime-archive@megatron.ietf.org
Delivered-To: ietfarch-dime-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05C173A6B60; Wed, 24 Dec 2008 01:30:16 -0800 (PST)
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 817EC3A6B60 for <dime@core3.amsl.com>; Wed, 24 Dec 2008 01:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[AWL=0.837, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OLZgSiloSNKb for <dime@core3.amsl.com>; Wed, 24 Dec 2008 01:30:13 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C39673A67B1 for <dime@ietf.org>; Wed, 24 Dec 2008 01:30:12 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KCD00J01JJPE2@szxga03-in.huawei.com> for dime@ietf.org; Wed, 24 Dec 2008 17:26:13 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KCD001CQJJPAL@szxga03-in.huawei.com> for dime@ietf.org; Wed, 24 Dec 2008 17:26:13 +0800 (CST)
Received: from z24109b ([10.70.39.116]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KCD0053GJJPI5@szxml06-in.huawei.com> for dime@ietf.org; Wed, 24 Dec 2008 17:26:13 +0800 (CST)
Date: Wed, 24 Dec 2008 17:26:12 +0800
From: Tina TSOU <tena@huawei.com>
To: dime@ietf.org, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Message-id: <00d201c965a9$a9fd2db0$7427460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <011c01c964e8$922f3f50$0201a8c0@nsnintra.net>
Subject: Re: [Dime] FW: DIME Milestones Update
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1258159858=="
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org

Hi all,
Should the work in
http://groups.google.com/group/diameter-routing
be considered at the same level as the following?

- "Diameter User-Name and Realm Based Request Routing Clarifications"
    (based on
http://tools.ietf.org/id/draft-korhonen-dime-nai-routing-02.txt) 

Wish you a joyful and peaceful holiday season and a prosperous and healthy New Year:D

B. R.
Tina
  ----- Original Message ----- 
  From: Hannes Tschofenig 
  To: dime@ietf.org 
  Sent: Tuesday, December 23, 2008 6:23 PM
  Subject: [Dime] FW: DIME Milestones Update


  Hi all, 

  I had a chat with Dan about the adjustments of the milestones and I crafted
  the following list: 

  --------------------------------

  DONE.......Submit "Diameter API" to the IESG for consideration as an
  Informational RFC 

  DONE.......Submit "Diameter Mobile IPv6: Support for Network Access Server
  to Diameter Server Interaction" to the IESG for consideration as a Proposed
  Standard. 

  DONE.......Submit "Quality of Service Parameters for Usage with Diameter" to
  the IESG for consideration as a Proposed Standard. 

  Dec 2008...Submit "Diameter Mobile IPv6: Support for Home Agent to Diameter
  Server Interaction" to the IESG for consideration as a Proposed Standard. 

  Jan 2009...Submit Revision of "Diameter Base Protocol" to the IESG for
  consideration as a Proposed Standard 

  Jan 2009...Submit "Quality of Service Attributes for Diameter" to the IESG
  for consideration as a Proposed Standard

  Jan 2009...Submit "Diameter QoS Application" to the IESG for consideration
  as a Proposed Standard

  Jan 2009...Submit "Diameter Support for EAP Re-authentication Protocol" as
  DIME working group item

  Jan 2009...Submit "Diameter User-Name and Realm Based Request Routing
  Clarifications" as DIME working group item

  Jan 2009...Submit "Diameter Proxy Mobile IPv6" as DIME working group item

  Mar 2009...Submit "Diameter Application Design Guidelines" to the IESG for
  consideration as a BCP document 

  Apr 2009...Submit "Diameter User-Name and Realm Based Request Routing
  Clarifications" to the IESG for consideration as a Proposed Standard

  Apr 2009...Submit "Diameter Proxy Mobile IPv6" to the IESG for consideration
  as a Proposed Standard

  May 2009...Submit "Diameter Support for EAP Re-authentication Protocol" to
  the IESG for consideration as a Proposed Standard

  --------------------------------

  A few notes regarding the items: 

  * in the current milestones list at
  http://www.ietf.org/html.charters/dime-charter.html we do not have 'QoS
  Attributes for Diameter' and 'QoS parameters for Usage w/ Diameter'. Some
  time back we decided to split the Diameter QoS work into three documents and
  I believe we should capture this aspect in the updated milestone list. 

  * There are 3 new items in the list, namely 
    - "Diameter Support for EAP Re-authentication Protocol"
      (based on
  http://tools.ietf.org/id/draft-dondeti-dime-erp-diameter-02.txt) 
    - "Diameter User-Name and Realm Based Request Routing Clarifications"
      (based on
  http://tools.ietf.org/id/draft-korhonen-dime-nai-routing-02.txt) 
    - "Diameter Proxy Mobile IPv6"
      (based on http://tools.ietf.org/id/draft-korhonen-dime-pmip6-04.txt) 

  * When writing the above list I was wondering whether we actually need to go
  for Proposed Standard for these three documents. With RFC3588bis we could
  also use Informational RFCs and then upgrade them once we got implementation
  and deployment experience. I believe that this would allow us to publish
  documents faster. I wonder what the group thinks about that idea? 

  * I made a proposal regarding the milestones and I was wondering whether the
  group considers my suggestion as realistic. 

  Ciao
  Hannes

  _______________________________________________
  DiME mailing list
  DiME@ietf.org
  https://www.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime