Previous PageNext Page

Chapter 3 - StreetTalk Naming Service


What Is StreetTalk?

StreetTalk Names

Figure 3-1. Names and Resources

Constructing Names

Figure 3-2. Items, Groups, and Organizations

Sample Names

Table 3-1. Sample StreetTalk Names

How StreetTalk Distributes Information

StreetTalk Database

Group Tables

Distributing Information

Example Three Groups Maintained on Two Servers

Figure 3-3. Sample Names

Creating StreetTalk Names

Format of StreetTalk Names

Figure 3-4. Valid StreetTalk Names

Valid Characters in a StreetTalk Name

Standard 7-bit alphanumeric characters A through Z, a through z, and 0 through 9.
7-bit non-alphanumeric characters such as the period, comma, space, and dash.
8-bit characters that include accents, diacritical marks (for example, a circumflex), and other special characters for language-specific characters. These 8-bit characters are part of a character set known as the PC multinational character set.
Any character that you enter from your keyboard can be stored and displayed on a workstation screen by VINES. Names for servers, groups (the second part of a StreetTalk name), and organizations (the third part of a StreetTalk name) cannot contain PC multinational 8-bit characters.

Thomas M. Chang@MrktRes@WCTUS


How to Specify Names

Creating unique names
Naming items (users and services)
Naming groups
Naming organizations

Unique Names

Naming Users


Item names should be unique within groups.
Group names should be unique within organizations.
Organization names should be unique to networks or internetworks.

StreetTalk names must total 31 characters or less (i.e., item, group, organization, and @ signs).
Passwords must be 8 characters or less.
If a user enters a StreetTalk name in the Chooser that is longer than 31 characters, that user will not be able to log in.


Jerry P. Shaughnessy


General Nickname Rules

User Name Worksheet

Figure 3-5. User Name Worksheet

Naming Groups

Creating Groups

Ricardo Flores@Finanzas@WCTES (Spain)
Diane Baillargeon@Finances@WCTCA
Wilhelm Meier
@Finanzen@WCTDE (Germany)

Performance Guidelines

If possible, each user should belong to a group that is maintained on a server with a direct LAN connection to the user's workstation. This approach yields better performance, especially for logins. User profile information, processed at login, is kept on the server that maintains the user's group.
In smaller networks with few users and groups, try to put users in the same group as the services they use most often.
In larger networks with many groups that are very large, you may have to put related groups and users on more than one server and let more than one StreetTalk service manage them.

As groups and organizations are added to the network in this way, the memory needs of each StreetTalk service in the network increases and can adversely affect the performance of a server. In general, a server can have a maximum of 25 groups, but that number varies depending on the services you run and how intensively users access the system.

Naming Organizations

Corporate Example

Report Program

Special StreetTalk Features

Working with the default group and organization
Guaranteed Login
Searching for names
Using StreetTalk patterns
Working with lists and AdminLists
Managing attributes

Default Group and Organization

Default Organization

Default Group for Administrators

StreetTalk Guaranteed Login

Searching for Names

Using StreetTalk Patterns

Example Searching for a Pattern



Working with Lists

Distribute mail
Designate administrators (AdminLists)
Assign access rights lists for print services, information stored on a file volume, or connections to host computers

Names of Lists

For example, suppose you belong to the group Sales@WCTUS. You often send identical mail messages to Patricia Jones@Sales@WCTES, Richard Moulan@Ventes@WCTCA, and Klaus Schmidt@Verkauf@WCTDE. You can create this list:



Example Group and Server Administrators

Figure 3-6. Group and Server AdminLists

Table 3-2. WCT AdminLists

AdminList Guidelines

Limit the number of names on AdminLists. The more names you add to AdminLists, the less secure your network is.
Be careful how you use lists. Do not create lists that attempt to serve more than one purpose. For example, if you create a list for mailing, do not use that same list to assign access rights to a file volume. Users whom you want only to receive mail may inadvertently be given rights to files and directories.
AdminLists that include users on remote servers (for example, servers across X.25 or WAN lines) can degrade network performance because the system is required to validate those names. Do not put the names of users who are located across WAN links on AdminLists.
Always record the names of all administrators.
In addition to the names of real users, consider creating a fictitious administrator for use in case of an emergency. For example, every server could have the user Backup Admin@Servername@Servers. This user must have a blank user profile and must be password protected. (A blank profile helps prevent a login from getting hung up.) Profiles are explained in Chapter 6.
An AdminList must have at least one name, but that name should not be a name that is stored on another server. If the other server is removed from the network or stops, the administrator of your group on your server disappears.

AdminList Planning Worksheet

Figure 3-7. AdminList Planning Worksheet


Note: When you manage the attributes of a StreetTalk resource, the resource is referred to as an object. For example, John Blake@Admin@WCTAR is a StreetTalk object.

Default Attributes

Mail stop
Language (English, German, French, and so on)


Mail stop
P.O. box
Postal code
Street address

Management and User Programs

Administrator's Check List

Assign names and nicknames to users.
Select names for groups and organizations.
Assign users to groups and groups to organizations.
Locate groups on servers.
Decide who will be on the group and server AdminLists.
Read about STDA in Chapter 8.

Key Terms

Further Reading

Previous PageTop Of PageNext Page