2.4.15 Roaming Operations (roamops)

NOTE: This charter is a snapshot of the 40th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 24-Oct-97


G. Zorn <glennz@microsoft.com>
Pat Calhoun <pcalhoun@usr.com>

Operations and Management Area Director(s):

John Curran <jcurran@bbn.com>
Michael O''Dell <mo@uu.net>

Operations and Management Area Advisor:

John Curran <jcurran@bbn.com>

Technical Advisor(s):

Michael O''Dell <mo@uu.net>

Mailing Lists:

General Discussion:roamops@tdmx.rutgers.edu
To Subscribe: roamops-request@tdmx.rutgers.edu
In Body: include
Archive: ftp://ftp-no.rutgers.edu/misc/IETF/roamops

Description of Working Group:

The purpose of this group is to develop or adopt procedures, mechanisms and protocols to support user roaming among groups of Internet service providers (ISPs). This is different from, but related to, the work of the IP Routing for Wireless/Mobile Hosts Working Group (mobileip) in that the roamops group is not concerned with the movement of hosts or subnets, but of users. In the near term, the goals of the group will be to produce an architectural document describing the basic mechanisms required to support user roaming. A repository for documentation describing current roaming implementations will also be maintained.

In addition, the group will address interoperability among ISPs and roaming users by standardizing such items as network usage data exchange (including the content, format and protocols involved), phone book attributes and exchange/update protocols, inter-ISP authentication mechanisms and exploring in depth the security issues involved with roaming. This work is expected to consist mainly of new or revised procedures and application-layer protocols.

Any and all business issues regarding the operation of an ISP roaming network (such as settlement, business and billing methods) are specifically NOT in the scope of the roamops Working Group and will not be discussed.

The group will work closely with other IETF Working Groups (including mobileip, radius, nasreqng saag and cat) to identify issues to which the roamops group should attend, as well as to assure their work does not make roaming unnecessarily difficult or impossible.

The utmost goal of the group will to make sure, by any means necessary, that it produces documents of high quality that are useful to the IETF community.

Goals and Milestones:



Re-submit existing Internet-Drafts as work of the ROAMOPS Working Group

Jan 97


Submit Internet-Drafts to IESG for publication as RFCs



Review the charter for additional work required

Jul 97


Submit the roaming implementations review draft for publication as an Informational RFC.

Sep 97


Submit the roaming requirements and network authentication identifier drafts for publication as a Proposed Standard.

Oct 97


Submit Internet-Drafts on phone book attributes and format.

Dec 97


Submit the authentication draft for publication as a Proposed Standard.

Feb 98


Submit the accounting draft for publication as a Proposed Standard.


Request For Comments:







Review of Roaming Implementations

Current Meeting Report

Minutes of the Roaming Operations (ROAMOPS) WG

At the meetings, we decided to move the NAI draft to last call. We also decided to update the charter since it is out of date.

At the Munich IETF, we decided to hold off on the Roaming Requirements draft since we were uncomfortable with the security issues which were raised in the mailing list. Now that we understand the security issues Bernard Aboba will update the document and move it to last call.

A milestone was reached within the WG. We identified that the current "defacto" authentication/accounting protocol, RADIUS, does NOT meet the requirements set in the roaming requirements draft. It was decided that RADIUS will be removed from the requirements draft and it will no longer be considered as a protocol to suit ROAMOPS needs.

The roaming requirements draft will also be updated to include the latest phonebook requirements.


None Received

Attendees List

go to list

Previous PageNext Page