Ariadne Conill
Ariadne Conill
Right. But not the specific tags themselves.
The advantage to getting the IETF to sign off on a base spec is that they would deprecate 1459 and 2810-2813 in the process. However, one could argue that Richard...
In charybdis, we plan to implement `rfc7700` "casemapping", which is the same as rfc3454 nameprep except using IDN2008 rules, with specific requirements for "nicknames".
> How are we going to maintain the backward compatibility? There is no plan in charybdis for backwards compatibility. Deployments which switch from `rfc1459` to `rfc7700` casemapping will assume clients...
Proposed client behaviour would be in a non-normative part of the spec at best, so it's not even worth bothering with. I suspect with the way this discussion is going,...
[rfc7700](http://tools.ietf.org/html/rfc7700), when properly implemented, handles all of those issues and more. have you read it?
@kythyria wrote: > @M2Ys4U TCP guarantees in-order delivery, so the server doesn't need to add a tag to every message, thus saving bandwidth. TCP does not guarantee _delivery_. It only...
This issue was discussed at today's IRCv3 coordination meeting. The conclusion is that a numerics registry service will be created, and then from there we will do the allocations once...
I would prefer a verb other than `FLAGS` for this, otherwise +1.