2. © 1998 R. Gemmell IETF WG Presentation1 Robert Gemmell ROAMOPS Working Group

3. © 1998 R. Gemmell IETF WG Presentation2 Introduction The purpose of the ROAMOPS working group is to provide a set of protocols for the provision of “roaming capability” for dialup Internet users. “Roaming capability” is the ability to access the Internet through multiple ISPs while maintaining a customer-vendor relationship with just one.

4. © 1998 R. Gemmell IETF WG Presentation3 Introduction cont. This group does not exist to dictate business issues such as billing methods, but will propose standards for interoperability between ISPs and roaming users. The storing, exchange, and update of phone number lists will be priority issues for this group. The URL for this group is: http://www.ietf.org/html.charters/roamops-charter.html To subscribe to the mailing list: roamops-request@tdmx.rutgers.edu

5. © 1998 R. Gemmell IETF WG Presentation4 Internet Draft for Roaming Requirements This draft describes the basic architectural framework for the standardization of roaming capabilities. It prescribes three basic subsystems: - Phone Book - Authentication - Accounting This document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-roamops- roamreq-08.txt

6. © 1998 R. Gemmell IETF WG Presentation5 The Phone Book The phone book system allows for secure and reliable access to a list of phone numbers customers of an ISP may utilize. The phone book system may be viewed as four separate pieces: - presentation - exchange - compilation - update

7. © 1998 R. Gemmell IETF WG Presentation6 Phone Book cont. The presentation, exchange, and compilation systems can implement different approaches according to vendor preference. Because the update process must be independent of any operating system or platform, it needs to be standardized. Security issues such as server authentication and data integrity must also be dealt with.

8. © 1998 R. Gemmell IETF WG Presentation7 Authentication Authentication of a host’s identity and that of their ISP must be required. The authentication system may be broken into five pieces: - connection management - authentication - NAS configuration/authorization - address assignment/routing - security

9. © 1998 R. Gemmell IETF WG Presentation8 Authentication cont. A standard connection protocol must exist to allow users to connect to ISPs other than their own. Networks must be assigned an ID and users must receive an ID from their formal ISP. The NAS needs to be able to verify both the network ID and user ID.

10. © 1998 R. Gemmell IETF WG Presentation9 Authentication cont. After verification of identity, the host must be assigned an IP address. Again, security is a big issue for the authentication process. Only authorized users should be able to gain access to the NAS. The host must not accept any data from an unauthorized server.

11. © 1998 R. Gemmell IETF WG Presentation10 Accounting A standard format must be set up for keeping track of who used what resources and for how long. This format must provide adequate security for transmission of the accounting data. Room must be provided for future expansion of the length of the accounting record.

12. © 1998 R. Gemmell IETF WG Presentation11 RFC 2194 This document is a review of existing roaming implementations and their functionality. Many of the issues from the previously mentioned Internet Draft are discussed here. Existing software applications such as AimTraveler and I-Pass Dial Wizard are examined as samples of what the protocol should include.

13. © 1998 R. Gemmell IETF WG Presentation12 RFC 2194 cont. The focus of this RFC is to advertise the benefits of using the products examined within it. It is essentially nothing more than an alteration of the previously mentioned Internet Draft with a description of the related products sold by the companies the authors of this document work for.

14. © 1998 R. Gemmell IETF WG Presentation13 42nd IETF Meeting No meeting has been scheduled for the 42nd IETF in Chicago.