Group,
Here are a few stupid/nit questions,
1) What do you do with host naming collisions?
2) Is a blank "string" blank equal to a "string"?
3) Is the hostname case sensitive?
4) Since the hostnames are "human readable", would
a backspace within the name make logical sense?
5) Don't some system implement x chars per tab,
then how do we show a consistent hostname?
6) If bell is included, does the system need to create
a sound each time the name is displayed?
7) If the router is localized to a different country, wouldn't
a logical hostname representation be able to support
multi-character and multi-byte foreign languages?
8) Underline support?
Thus, IMO, someone needs to re-write part of this to equal
http(s) URL type representation? or only alphanumeric chars
And specify some sort of left/right printing justification and
a way to deal with non printable chars..
Mitchell Erblich
===================
On Jun 2, 2009, at 2:37 PM, The IESG wrote:
The IESG has received a request from the Open Shortest Path First
IGP WG
(ospf) to consider the following document:
- 'Dynamic Hostname Exchange Mechanism for OSPF '
<draft-ietf-ospf-dynamic-hostname-03.txt> as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to
the
ietf(_at_)ietf(_dot_)org mailing lists by 2009-06-16. Exceptionally,
comments may be sent to iesg(_at_)ietf(_dot_)org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ospf-dynamic-hostname-03.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17203&rfc_flag=0
_______________________________________________
OSPF mailing list
OSPF(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ospf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf