In message <199604051733.MAA28893@merit.edu>, Brian Renaud writes:
Some issues which seem to require further discussion:
<string> length Should we require the <string> to be more than one character long? That is, should as-macro names such as "AS-A" be illegal? If we require more characters, how many more should we require? Alternatively, we could rely on commun- ity pressure to discourage meaningless names.
ending characters Should we require as-macro names to end in an alphabetic letter or digit? That is, should names such as "AS-ISP_" be illegal? Alternatively, we could rely on community pressure to discourage such apparently badly formed names.
case sensitivity Should the comparisons of as-macro names be case insensi- tive? That is, should the database software consider the as-macro name AS-EBONE to be the same as the as-macro name as-ebone?
Pick something and let's move on to real problems.
3.3. Discussion Points
Some issues which seem to require further discussion:
community name length Should we require the community names to be to be more than one character long? That is, should community names such as "x" be illegal? If we require more characters, how many more should we require? Alternatively, we could rely on community pressure to discourage meaningless names.
ending characters Should we require community names to end in an alphabetic letter or digit? That is, should names such as "ISP- Backbone_" be illegal? Alternatively, we could rely on com- munity pressure to discourage such apparently badly formed names.
case sensitivity Should the comparisons of community names be case insensi- tive? That is, should the database software consider the community name WCW to be the same as the community name wcw?
Same here. I'm don't favor syntax checking for asthetically pleasing names, but I don't plan to use really ugly ones either. Go either way. Curtis