Agenda
  - Charter Review
  - Document Status
  - Network Access Identifier - Draft 12
  - Do we need a more complex NAI
  - Accounting Data Interchange Format (ADIF) - Draft 5
  - Mobile IP and the NAI 
  - XML Phone Book
  - Alternative Roaming Applications

Charter Review
  We are almost complete with the work that is on the charter. There are two 
errors in the charter. There was a double "in in" and the last paragraph:
"The utmost goal of the group will [be] to make sure"

Document Status

Roaming Requirements - This document was approved by the IESG and is sitting
on the RFC editor's desk.

Proxy Chaining - Should this document remain in the standards track, or be
published as informational. This document has some serious security problems,
which should be stated. Consensus was to change the document as informational 
and move it along. Last call next monday to hopefully be published next month.

The document must include a paragraph to state the WG's feeling about the 
document. The -09 document will be available in 1/99.

LDAP Phonebook - This document has expired and will not be updated. The idea is
to send out another version that uses XML instead.

End-to-end - Mention of RADIUS should be removed and the document could simply
define the methods that provide end-to-end security. We will discuss on the 
list.

2. Do we need a more complex NAI? / John Vollbrecht

The problem today is that there is no way for a user to "select" the broker
to be used (e.g. choosing Visa rather than Discover). Many providers are
currently using "broker/user@domain". Since this is being used in many 
networks, should we standardize an extended format.

It has been stated that this is a kludge, and if a document was published
to describe this, it should be stated in the document. Another solution is to
have different domains when a user wants to have multiple brokers. 

Paul Funk will write an Internet-Draft to describe the NAI Prefix.

Does this belong in the requirements? Since it is optional, it does not 
necessarily make it a requirement. Since the requirements draft is on the
RFC editor's chair, let's not do it right now. This may become a requirement
in the future.

3. ADIF 

The last draft has cleaned up text and includes the IANA considerations. 
Next Monday a WG last call will be done.

4. Mailing List silence

A plea from Glen to have people participate on the mailing list. The current
trend, to wait until last call is slowing the progress of the working group. 

5. XML and Phone Book

Glen has let the LDAP phone book draft expire and wishes to to send another 
version of the draft which translates all of the attributes to XML. There was
a positive comment, but we do not have any expertise with XML. We are looking
for a document editor with XML experience. The plea will be extended to the
list.

Maximilian Riegel [Maximilian.Riegel@icn.siemens.de] has volunteered to
take ownership of this work item.

6. Alternative Roaming Applications and Mobile IP

The WG has decided that we will be looking at new applications because it fits
within our charter. We will work on the security model for roaming to ensure 
that it is solved for all applications.

However, we must be sure that we do not lose focus and finish up our WG items
before we pick up new work.