This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
- Previous message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Wed Sep 25 23:57:11 CEST 2013
On Wed, Sep 25, 2013 at 11:45 PM, Leo Vegoda <leo.vegoda at icann.org> wrote: > Is ASCII format a synonym for plain text or is the proposal actually to > force the use of ASCII rather than a more modern character encoding? As of right now, it really does mean ASCII as full UTF-8 was too controversial and there was no hard need for it. FWIW, IETF is moving towards having the actual text in ASCII-only and allowing UTF-8 in metadata like author names. This allows easing in something new while still remaining 100% backwards-compatible. For the record, I am fine with all three of those options and will not push towards any of those. Whichever has the highest likelihood of reaching consensus has my support. There already has been a _lot_ of effort behind the scenes and I would like to see this implemented ASAP :) -- Richard
- Previous message (by thread): [ncc-services-wg] Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]