> Max, Glen... I would like to suggest you consider adding the "printer URL"
> (ippURL?) to the list (below) of elements in the address book. This would
> indicate the URL for sending print jobs via the Internet Printing Protocol
> (see RFCs 2565, 2566 or the current Internet Drafts
> http://www.ietf.org/internet-drafts/draft-ietf-ipp-model-v11-04.txt ,
> http://www.ietf.org/internet-drafts/draft-ietf-ipp-protocol-v11-03.txt ).
> Pragmatically, it will allow the entry to reflect one's "favorite printer"
> just as the current definition carries the preferred "fax number".
I'm confused. The FAX number below is not a "preferred" FAX #, it's the
_only_ FAX number for the provider. I'm not sure what the purpose of
putting a printer URL in the provider element would be (except maybe to
irritate ISPs by running jobs on the office printer ;-): the printer would
almost certainly be somewhere far from the roaming user.
> <!ELEMENT provider (
> supportPtr* )>
> <!ATTLIST provider
> id ID #REQUIRED>
> Harry Lewis
> IBM Printing Systems
> Maximilian Riegel <firstname.lastname@example.org> on 10/25/99 10:59:40
> To: email@example.com
> cc: "Zorn, Glen" <firstname.lastname@example.org>, "Calhoun, Patrice" <email@example.com>
> Subject: New internet draft: 'draft-ietf-roamops-phonebook-xml-02.txt'
> I have send a new version of the phone book draft named
> 'draft-ietf-roamops-phonebook-xml-02.txt' to the IETF. It should
> appear on the list and in the archives in a few days.
> A comprehensive revision of the last draft was undertaken to fix the
> items mentioned in Oslo and on the mailing list. What's changed:
> - Addition of a introductory paragraph emphasizing the application of
> the phone book as standard format for exchanging information between
> providers and the roaming consortium as well as between the roaming
> consortium and the users.
> - Usage of XML attributes for several elements to achieve a more
> readable and compact representation of the phone book. In addition the
> assigned values of XML attributes can be syntactically checked by a
> XML Editor enforcing the compliance with the specification of the DTD
> (document type definition). Even more by putting the attribute
> definitions into a separate document and importing it by an external
> reference into the DTD, extensibility of the specification without
> modification of the basic DTD is achieved. This structure allows IANA
> to maintain the attribute value space of the phone book.
> - Refinements of several elements, e.g. the number of occurrences
> allowed for the elements in the setup element, or the predefined
> values for the attribute "type" of the "pop"-element "address" (former
> - Revision of the complete DTD according to the modifications
> introduced by this version.
> - Addition of a chapter "IANA considerations" (needs some more
> - Addition of a chapter containing simple examples of a roamops phone
> As always:
> Comments are kindly appreciated.