EditWYSIWYGAttachPrintable
r18 - 08 Jan 2008 - 15:39:39 - HannesTschofenigYou are here: TWiki >  Dime Web  >  IetfDimeRoadMap > DimeStatusUpdate

Status Reports DIME WG

Report January 2008

Date: 8 January 2008

RFC3588bis

4 reviews: mostly editorial

Plan is to send an updated version around within the next 2 weeks.

Hannes is going to talk to Hannu about the lack of reviews from the 3GPP.

Diameter MIPv6: NAS - HAAA Support

(Short) 2nd WGLC has been started and forwarded to other WGLCs.

Diameter MIPv6: HA - HAAA Support

Updated draft will be published 2 weeks.

Quality of Service Parameters for Usage with the AAA Framework

Text based on the discussions regarding the IANA registry needs to be provided. Draft update within the next 2 weeks.

Quality of Service Attributes for Diameter

Plan is to send an updated version around within the next 2 weeks.

Subsequently a 2nd WGLC will be initiated.

Diameter QoS

Resubmit a new draft version this week.

Diameter Applications Design Guidelines

Dave will review the document this week. Update will be done in the following 2 weeks. Then, the document should be ready for a 4 weeks WGLC (4 weeks since we are going to involve other SDOs).

The 3GPP work on Diameter design guidelines can be found here: http://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-020.zip

Diameter API

Resubmit the draft to fix a reference and submit PROTO writeup

Diameter Credit Control Test Case

Dan is going to sponsor the document. Tolga is going to review by the end of this week.

The document is needed by the OMA.

Diameter Policy Processing Application

draft-brenner-dime-peem is an AD sponsored document that has been submitted for publication.

Next IETF Meeting is approaching

Hannes to post a plan about the selection of new work.

Report November 2007

Date: 20 November 2007

RFC3588bis

No open issues. 4 weeks last call starting 20th November 2007. WGLC will also be sent to OMA, TISPAN, 3GPP, ITU-T

Diameter MIPv6: NAS - HAAA Support

Update submitted. Clarification only. 2nd WGLC not necessary.

Diameter MIPv6: HA - HAAA Support

Update submitted 2nd WGLC necessary (4 weeks) WGLC will also be sent to 3GPP, 3GPP2, WIMAX

Quality of Service Parameters for Usage with the AAA Framework

1st WGLC raised some misalignment between TSVWG and NSIS regarding the registry allocation

AI: Send a mail to the TSVWG and NSIS chairs, Transport ADs & Dan AI: Give a presentation about the DIME work in the next RADEXT session at IETF#70. Migration strategy for the RADIUS to Diameter is that Diameter supports all the RADIUS functionality.

Quality of Service Attributes for Diameter

Update based on 1st WGLC. 2nd WGLC necessary

Diameter QoS

Updated document with more details on push scenario. Framework related parts removed. Not clear how to treat the framework related aspects.

Diameter Applications Design Guidelines

Updated document; one more version needed (after Vancouver); additional guidance with regard to the AVP flag table will be provided. WGLC in December

Raise alignment with 3gpp with Hannu

Diameter API

Hannes went through the document to prepare a PROTO writeup. In consultation with Victor a couple of issue with regard to the literature references, formal language for the C-alike syntax and other PROTO review criteria were discovered. A draft update is necessary to fix these bugs before the PROTO writeup will be sent to the IESG. Update planned around the IETF#70 meeting.

Charter & Milestone Update

Updated. discussions and preparation work during the meeting in Vancouver. Rechartering will most likely be done during Jan. 2008.

Report October 2007

Date: 22 October 2007

RFC3588bis

However, a couple of new issues got posted to the list, and resolved. A draft update with these changes is imminent.

Both open issues from the last month are still open.

Diameter MIPv6: NAS - HAAA Support

The WGLC was done as planned. A new draft update is not necessary.

Diameter MIPv6: HA - HAAA Support

The WGLC was initiated as planned, see http://www1.ietf.org/mail-archive/web/dime/current/msg02063.html

A few comments were received that require a draft update.

Quality of Service Parameters for Usage with the AAA Framework

The WGLC was initiated as planned, see http://www1.ietf.org/mail-archive/web/dime/current/msg02062.html

Based on the review comments a new version of the document has to be prepared. The discussions are, however, still in progress.

Quality of Service Attributes for Diameter and RADIUS

The WGLC was initiated as planned, see http://www1.ietf.org/mail-archive/web/dime/current/msg02064.html

Based on the review comments a new version of the document has to be prepared. The discussions are, however, still in progress.

Diameter QoS

The document needs to cover the push and the pull scenario. The framework specific part that explain how the different documents fit together will be moved into a framework specific document (at least that's the current proposal).

Diameter Applications Design Guidelines

Draft update was submitted to improve the presentation style. The planned WGLC (Dec. 2007) is still accomplishable.

Charter & Milestone Update

We need todo a short milestone update now. Then, after we sent a few documents to the IESG we should recharter.

Report August 2007

Date: 19 August 2007

During the last month there was the IETF meeting. The meeting minutes are here: http://www3.ietf.org/proceedings/07jul/minutes/dime.txt

RFC3588bis

There are two open issues with RFC3588bis:

Planned WGLC: End of October 2007

Diameter MIPv6: NAS - HAAA Support

No open issues known

Planned WGLC: August 2007

Diameter MIPv6: HA - HAAA Support

The introduction of the MIPv6 Auth protocol support damaged the structure of the document a bit. The document structure needs to be revisited. This work is currently ongoing.

Planned WGLC: October 2007

Quality of Service Parameters for Usage with the AAA Framework

A minor update regarding the QoS parameters is necessary. This update will be provided within the next 2 weeks.

Planned WGLC: September 2007

Quality of Service Attributes for Diameter and RADIUS

This document also requires an update regarding the alignment with the QoS parameters. The support of RADIUS is still pending and might introduce problems given the currently selected attribute encoding.

Planned WGLC: September 2007

Diameter QoS

Action item for Hannes: Determine next steps for a potential document restructuring.

Planned WGLC: Unknown

Diameter Applications Design Guidelines

It is necessary to create another draft update to reflect recently received review comments, namely:

  • More clarification on application versioning using optional avps.
  • Comments centered around vendor specific command code allocation
  • Editorials.

When the WGLC is issued then the document will be sent for review to other SDOs, such as 3GPP, OMA, ITU-T, TISPAN, and 3GPP2.

Planned WGLC: December 2007

AAA Framework for Multicasting

A request for review has been received relating to the document "AAA Framework for Multicasting" which is under development within the MBONED WG. The document is available for inspection here: http://www.ietf.org/internet-drafts/draft-ietf-mboned-multiaaa-framework-04.txt

We appointed the following reviewers:

  • Jouni Korhonen
  • Tina Tsou

More reviewers are welcome.

Report July 2007

Date: 16 July 2007

This report covers June 2007 and the first two weeks of July 2007 (till the draft submission deadline).

Diameter Mobility

We have made progress with both mobility documents. Here are the updated versions:

Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-04.txt

Changes between -01 and -04: http://tools.ietf.org/rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-dime-mip6-split-01.txt&url2=http://tools.ietf.org/id/draft-ietf-dime-mip6-split-04.txt

  • Editorial Changes
  • The draft now addresses the Mobile IPv6 Authentication Option as requested by MIP6 WG participants. The AVPs have been re-used from RFC 4004.
  • Accounting part is now specified.
  • There are two usages defined in the document now:
    • Diameter EAP is used for bootstrapping with IKEv2 (for the authentication part).
    • A new application defined for usage with the Mobile IPv6 Authentication Option.
  • The MIP6-Feature-Vector AVP is imported from draft-ietf-dime-mip6-integrated-05.txt

Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integrated-05.txt

Changes between -03 and 05: http://tools.ietf.org/rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-dime-mip6-integrated-03.txt&url2=http://tools.ietf.org/id/draft-ietf-dime-mip6-integrated-05.txt

  • Two AVPs from RFC 4004 have been re-used: MIP-Home-Agent-Address & MIP-Home-Agent-Host
  • A MIP6 feature vector has been introduced that plays the role of a capability indicator
  • Example updated
  • Editorial changes

Particularly with the alignment with the Diameter Mobile IPv4 Application http://www.ietf.org/rfc/rfc4004.txt is important when it comes to the support for the Mobile IPv6 Authentication Option. The Authentication Protocol for MIP6 is described in these documents. http://www.ietf.org/internet-drafts/draft-ietf-mip6-rfc4285bis-00.txt http://www.ietf.org/rfc/rfc4285.txt

Another aspect is the alignment between the Mobile IPv4 Challenge/Response Extensions (Revised) (RFC 4721) http://www.ietf.org/rfc/rfc4721.txt and the Authentication Protocol for MIP6. We currently re-use the Diameter MIPv4 Application AVPs that are focused on RFC 4721 in the assumption that RFC 4721 and RFC 4285 are similar if not the same. It needs to be investigated whether this assumption is true.

There is also a RADIUS MIP6 document that needs to be aligned with the DIME working group documents. Here is the document: http://www.ietf.org/internet-drafts/draft-ietf-mip6-radius-02.txt The alignment has NOT yet been done.

Diameter QoS

The Diameter QoS application document has been updated http://tools.ietf.org/html/draft-ietf-dime-diameter-qos-01 and the main changes are: http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-dime-diameter-qos-01.txt

  • Additional author added, namely Dong Sun
  • Framework section updated. It now contains a discussion about different end point capabilities
  • Authorizing Entity definition updated
  • Push & Pull Mode term added
  • The authorization schemes section has been added again.
  • All AVPs that are now defined in http://www.ietf.org/internet-drafts/draft-ietf-dime-qos-attributes-01.txt have been removed from this document and a reference to them is included.

As you have seen from the discussions on the mailing list there are still some controversial issues around parts of the document.

Diameter QoS Attributes

This document has also experienced a major update. http://www.ietf.org/internet-drafts/draft-ietf-dime-qos-attributes-01.txt

Changes are:

http://tools.ietf.org/rfcdiff?url1=http://tools.ietf.org/wg/dime/draft-korhonen-dime-qos-attributes-00.txt&url2=http://tools.ietf.org/id/draft-ietf-dime-qos-attributes-01.txt

  • A number of examples have been added
  • All attributes are now defined and utilize the draft-ietf-radext-filter-rules-03 document.
  • A QoS-Capability AVP has been added to convey information about the available QoS models.

It is still an open issue whether this document should provide the corresponding RADIUS QoS functionality via the Diameter RADIUS Interoperability. The http://tools.ietf.org/wg/radext/draft-tschofenig-radext-qos-05.txt document is therefore out-of-date with respect to the alignment with the corresponding Diameter work.

Diameter Auditing

There are two active drafts on this topic:

Work on the mailing list is ongoing in matching the needs for state recovery identified in draft-asveren-dime-state-recovery-01 with mechanisms for resource management included into draft-bodin-dime-auditing-reqs-02 from draft-calhoun-diameter-res-mgmt-08 (expired). The result of this matching (including identification of additional mechanisms) will be presented at the Chicago meeting

Diameter API

The PROTO write-up has been written for http://tools.ietf.org/wg/dime/draft-ietf-dime-diameter-api/ and will be send to the IESG during this week.

Diameter Design Guidelines

http://www.opendiameter.org/public/draft-ietf-dime-app-design-guide-01-from-2.diff.html

A minor update was made between -00 and -01: http://tools.ietf.org/rfcdiff?url2=http://tools.ietf.org/id/draft-ietf-dime-app-design-guide-01.txt

After detailed review comments have been posted to the list the structure of the document was changed. The new document is here: http://www.opendiameter.org/public/draft-ietf-dime-app-design-guide-02.txt

The change history can be found here: http://www.opendiameter.org/public/draft-ietf-dime-app-design-guide-01-from-2.diff.html

Diameter Base Document

Two versions have been submitted in the last month.

The deltas between 04 and 05 versions are as follows:

  • 05 includes proposals for 20, 56, 57
  • Open issues: 35, 39, 55, 58

#35 and #39 are still open from previous revs. We probably need to get this resolved soon. Suggestions on how to do this is described below. #55 A change in command code allocation process. See editor's note in the bis document #58 Possible error in IANA registration. Should be easily fixed.

The diff's between 05 and 04 is available here: http://www.opendiameter.org/public/draft-ietf-dime-rfc3588bis-05-from-4.diff.html

The deltas between 03 and 04 versions are as follows: * proposals for open issue 34, 50, 54, 53 included

The issue tracker can be found here: http://www.tschofenig.com:8080/diameter-interop/index

Report June 2007

Date: 2nd June 2007

Diameter QoS

Dong Sun is working on an strawman proposal for the integration of http://www.ietf.org/internet-drafts/draft-ietf-dime-diameter-qos-00.txt and http://tools.ietf.org/wg/dime/draft-sun-dime-diameter-resource-control-requirements-01.txt

draft-korhonen-dime-qos-parameters-00.txt and draft-korhonen-dime-qos-attributes-00.txt will become working group items. The updated draft will consider the alignment with the ongoing filter rule work in RADEXT.

Diameter Mobile IPv6

A new version of the "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction" was submitted that addresses the previously open issues. The new draft version is here: http://tools.ietf.org/html/draft-ietf-dime-mip6-integrated-04

An update for the "Diameter Mobile IPv6: HA <-> HAAA Support" document is in progress. It will addres the open issues mentioned in the status update of last month.

Diameter Base Protocol Update

A new draft update is in progress. There are, however, a few tough issue left for discussion. Victor will send an update to the list.

Diameter API

A new version of the Diameter API was submitted that contain minor editorial fixes and template updates. A PROTO writeup is in progress and the document will be submitted to the IESG soon.

TISPAN Liaison

ACTION ITEM: Hannes to respond to liaison request

ITU-T Liaison

ACTION ITEM: Dave to respond to liaison request

Charter Update

ACTION ITEM: Hannes to check pending charter update.

Diameter Application Design Guidelines

We need reviews from the DIME WG for the document before we send it to other SDOs for review. Please volunteer!

Miscellaneous

Glen re-submitted his two MIB documents: http://tools.ietf.org/wg/dime/draft-zorn-dime-diameter-cc-appl-mib-02.txt http://tools.ietf.org/wg/dime/draft-zorn-dime-diameter-base-protocol-mib-02.txt

Report May 2007

Diameter QoS

ACTION ITEM: Hannes to propose next steps to the group. See http://www1.ietf.org/mail-archive/web/dime/current/msg01455.html

Diameter Mobile IPv6: NAS <-> HAAA Support

http://tools.ietf.org/html/draft-ietf-dime-mip6-integrated-03

The following changes will be made to the document:

  • Issue 3: Address Kuntal's concern on NASes that are not able to perform DNS query via indicating it in capability AVP.

ACTION ITEM: Hannes to ensure progress with Diameter mobility work.

Diameter Mobile IPv6: HA-to-AAAH support

http://tools.ietf.org/html/draft-ietf-dime-mip6-split-02

The following changes will be made to the document:

  • Issue A: Moving forward with one Application for Authn and Authz. Based on the recent consensus call, the WG agree to move with this. Yoshi is ok with moving in this direction.

  • Issue B: One or two command to support MIP6 Authentication Option as defined in RFC 4285. Julien posted a message regarding this issue: http://www1.ietf.org/mail-archive/web/dime/current/msg01399.html Madjid and Julien are in favor of having one command for EAP-Based and One command for RFC 4285-based authentication.

ACTION ITEM: WG members are invited to respond to the issue and to express their preference.

  • Issue C: How does the HA know if IKEv2 is used for VPN access or MIP6 service? Out-of scope of the document. However, we agree to add some text on this.

ACTION ITEM: Hannes to ensure progress with Diameter mobility work.

Diameter Base Protocol Update

As a short summary, the change history of http://www.ietf.org/internet-drafts/draft-ietf-dime-rfc3588bis-03.txt are as follows:

For easier reading the relevant diffs are:

The issue tracker can be found in: http://www.tschofenig.com:8080/diameter-interop/index

ACTION ITEM: Dave to ensure progress with Diameter Base Protocol work.

Diameter API

ACTION ITEM: Dave to publish an updated draft and to write PROTO writeup.

TISPAN Liaison

ACTION ITEM: Hannes to respond to liaison request

ITU-T Liaison

ACTION ITEM: Dave to respond to liaison request

Charter Update

ACTION ITEM: Hannes to check pending charter update.

-- HannesTschofenig - 08 May 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r18 < r17 < r16 < r15 < r14 | More topic actions
 
Powered by TWiki
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback