Secure Unowned Hierarchical Anycast Root Name Service - And an Apologia (was Re: [governance] Two IETF Internet-Drafts about human rights and censorship)

[McTim]

Wolfgang, All,

This article sheds light on the RFC in question:

http://www.circleid.com/posts/20141107_secure_unowned_hierarchical_anycast_root_name_service_and_apologia/

On Tue, Nov 4, 2014 at 3:19 PM, McTim <dogwallah at gmail.com> wrote:
> Wolfgang,
>
> Sorry I didn't get to say hello to you in L.A.!
>
> This is what was posted on DNS-OPS list last week:
>
> "Registration will open shortly for the Workshop on DNS Future Root
> Service Architecture.
>
>> Location: Hong Kong, HK
>> Date: December 8-9, 2014
>> Hosted by: ISOC-HK
>> Sponsors: ZDNS/BII and CNNIC
>> Co-chairs: Warren Kumari and Paul Vixie
>
> This two day workshop will focus on the DNS root service architecture
> issues raised by two current Internet Drafts:
>
> 1. http://tools.ietf.org/html/draft-wkumari-dnsop-root-loopback-00
>    Decreasing Access Time to Root Servers by Running One on Loopback
>    W. Kumari, Ed.; P. Hoffman
>
> 2. http://tools.ietf.org/html/draft-lee-dnsop-scalingroot-00
>    How to scale the DNS root system?
>    Xiaodong Lee; Paul Vixie; Zhiwei Yan
>
> These two drafts take very different approaches to the problem of
> increasing root zone availability to recursive name servers. In this
> workshop we will explore the differences and similarities, with an eye
> towards revising both drafts and clarifying their roles in the DNS
> root service architecture.
>
> Invitations including travel support will be extended to root name
> server operators (bcc'd here), and to the I-D authors. The workshop
> will be open to any interested party, and presentations will be
> streamed live and stored via Youtube. There will be no cost for
> attending the workshop. Pre-registration will be required.
>
> Information on how to register and on the proposed agenda will be sent
> shortly to this same distribution. For travel planning purposes, the
> meeting will run all day on December 8, with a social event that
> evening, and for half a day on December 9, finishing immediately after
> lunchtime."
>
>
>
> On Tue, Nov 4, 2014 at 10:21 AM, "Kleinwächter, Wolfgang"
> <wolfgang.kleinwaechter at medienkomm.uni-halle.de> wrote:
>> Thx. Stephane, this is useful and helpful.
>>
>> BTW, is there any discussion with rgard to the drafts on the number of root servers for the authoritative root? This was a (non-paper?) by Paul Vixie and two Chinese partners. What I have seen is that this was more or less watered down or rejected. Any news here?
>>
>> Thanks
>>
>> Wolfgang
>>
>> -----Ursprüngliche Nachricht-----
>> Von: governance-request at lists.igcaucus.org im Auftrag von Stephane Bortzmeyer
>> Gesendet: Di 04.11.2014 14:47
>> An: governance at lists.igcaucus.org
>> Betreff: [governance] Two IETF Internet-Drafts about human rights and censorship
>>
>> Next week is the 91th IETF meeting and, at the security meeting, these
>> two new Internet-Drafts will be discussed:
>>
>> https://tools.ietf.org/html/draft-doria-hrpc-proposal
>>
>>    Work has been done on privacy issues that should be considered when
>>    creating an Internet protocol [see the excellent RFC 6973, or
>>    working groups like DPRIVE, for DNS privacy. S.B.].  This draft suggests that similar
>>    considerations may apply for other human rights such as freedom of
>>    expression or freedom of association.  A proposal is made for
>>    initiating IRTF [Internet Research Task Force] work researching the
>>    possible connections between
>>    human rights and Internet standards and protocols.  The goal would be
>>    to create an informational RFC concerning human rights protocol
>>    considerations.
>>
>> https://tools.ietf.org/html/draft-hall-censorship-tech
>>
>>    This document describes the technical mechanisms used by censorship
>>    regimes around the world to block or degrade internet traffic.  It
>>    aims to make designers, implementers, and users of Internet protocols
>>    aware of the properties being exploited and mechanisms used to censor
>>    end-user access to information.  This document makes no suggestions
>>    on individual protocol considerations, and is purely informational,
>>    intended to be a reference.
>>
>>
>>
>>
>> ____________________________________________________________
>> You received this message as a subscriber on the list:
>>      governance at lists.igcaucus.org
>> To be removed from the list, visit:
>>      http://www.igcaucus.org/unsubscribing
>>
>> For all other list information and functions, see:
>>      http://lists.igcaucus.org/info/governance
>> To edit your profile and to find the IGC's charter, see:
>>      http://www.igcaucus.org/
>>
>> Translate this email: http://translate.google.com/translate_t
>>
>
>
>
> --
> Cheers,
>
> McTim
> "A name indicates what we seek. An address indicates where it is. A
> route indicates how we get there."  Jon Postel



-- 
Cheers,

McTim
"A name indicates what we seek. An address indicates where it is. A
route indicates how we get there."  Jon Postel

-------------- next part --------------
____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.igcaucus.org
To be removed from the list, visit:
     http://www.igcaucus.org/unsubscribing

For all other list information and functions, see:
     http://lists.igcaucus.org/info/governance
To edit your profile and to find the IGC's charter, see:
     http://www.igcaucus.org/

Translate this email: http://translate.google.com/translate_t