By "larger character set", do you mean 16-bit unicode? I can see where
that would be more general, but that will complicate implementations.
Also, it would be convenient of PIDs cannot contain "/", so PID names are
syntactically distinct from CIDRs. That simplifies configuration tables.
For example, a network map can be specified by a white-space-separated
sequence of PID names & CIDRs, where each CIDR is in the preceding PID.
Yes, of course I could use XML. But I find XML annoying to type, so I
prefer simpler alternatives whenever practical.
- Bill Roome
On 09/24/2011 14:19, "Richard Alimi" <[email protected]> wrote:
>Also, it has been requested that PID names also have a larger
>character set. Would there be any complaints with doing the same for
>PID names (with the existing rule still in place about '.')? The only
>(admittedly-small) concern I would have is that it might be confusing
>from a human-readability perspective if we ever did something with
>hierarchical PIDs and other punctuation characters were combined with
>the '.' in the same PID name.
>
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
