Re: Allowing IP addresses as path-identiites (Re: #1047 Path field delimiters and syntax - status)

["Charles Lindsey" <chl@xxxxxxxxxxxxxxxx>]

In <431EE668.3000402@xxxxxxxxxxxxxxx> "Forrest J. Cavalier III" <forrest@xxxxxxxxxxxxxxx> writes:

>Charles Lindsey wrote:
>> In <431DD5E2.5040802@xxxxxxxxxxxxxxx> "Forrest J. Cavalier III" <forrest@xxxxxxxxxxxxxxx> writes:
>> 
>> Yes, I made a proposal along those lines, except I put the keyword at the
>> end (because there is some existing practice for that). We can decide
>> after whether to follow that route (certainly the stuff in USEPRO covering
>> diagnostics needs a revision, and that might affect the precise syntax
>> too).

>Putting the keyword at the end makes it look like a TLD.  Starting with . makes
>it easy to determine it is not a bare FQDN.

If it were not for existing practice I would agree with you. But DNews (I
think, plus some others) regularly generates things like
...!news.example.com.MISMATCH!... in the Path, so I think it best to
formalize that usage rather then invent a different kind of wheel. I doubt
ICANN are on the verge of creating a "mismatch" TLD.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl@xxxxxxxxxxxxxxxx      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5