Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice

"Carlos M. Martinez" <carlosm3011@gmail.com> Thu, 29 May 2014 21:11 UTC

Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFD11A0228 for <ietf@ietfa.amsl.com>; Thu, 29 May 2014 14:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNQHw661ViDG for <ietf@ietfa.amsl.com>; Thu, 29 May 2014 14:11:32 -0700 (PDT)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB0101A0461 for <ietf@ietf.org>; Thu, 29 May 2014 14:11:32 -0700 (PDT)
Received: by mail-yk0-f172.google.com with SMTP id 79so775280ykr.31 for <ietf@ietf.org>; Thu, 29 May 2014 14:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4DgojcC5cKLvrb3TQl8Viyq/z7wgTkTeHADlFtOE158=; b=VFbYPFv2y2gU273TyJ0sSa41LtjnXxZZMCTJfz768pee91nx6bd/9tz8ZkccmWDZ6s XxhVVTrxHXhFf9OQjHtpR0yeAazP97u+MPP+ZDu5nvYzt9ZCtznZUVroQ+f1AF5zOpps yGcX/Wamalge6NqtH42NoeTm5wf74cXnBhKTVaqldxtVpD8R67vs/fEeHya7EuTYgnu4 +xacTueUbiY1UPOs3koqDER5UCI5I/OVZ/UYgspuXhoBKAa8s++ZQYLzCY8LlfNBAAD7 OGP3Ja4na1MgxADjKlMVylMPF6cmlmHixV7adqzO8RlPbT72gfy5w/ObwfzPOEkZvMpk F2dA==
X-Received: by 10.236.161.10 with SMTP id v10mr13920589yhk.27.1401397888416; Thu, 29 May 2014 14:11:28 -0700 (PDT)
Received: from albion.local ([2001:13c7:7001:7000:702d:feb2:766f:1988]) by mx.google.com with ESMTPSA id q66sm2720425yhj.44.2014.05.29.14.11.26 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 May 2014 14:11:27 -0700 (PDT)
Message-ID: <5387A27C.3030201@gmail.com>
Date: Thu, 29 May 2014 18:11:24 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice
References: <20140520204238.21772.64347.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140521194638.06eaf508@resistor.net> <1111FB79-012A-414B-B8CD-0BBDAE8BD6A8@hopcount.ca> <6.2.5.6.2.20140522095317.0c5fd648@elandnews.com> <5C02BCCA-79D7-40A5-BFB0-26284A667E78@vpnc.org> <DC9ED318-2352-4AF0-8A43-29D237C32B64@vigilsec.com> <924045CD-DC34-423B-8702-CD99CF687D46@vpnc.org> <31344.1401304682@sandelman.ca> <BF0C8B7B-27D0-40B8-8FBD-5D255951222F@ericsson.com> <538795FB.6060205@gmail.com> <4F62CE0A-114F-4285-B332-9D9EB2B38B42@isi.edu>
In-Reply-To: <4F62CE0A-114F-4285-B332-9D9EB2B38B42@isi.edu>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/t0Eqcx36moRKktaGA-ebA5lnOh0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2014 21:11:42 -0000

Hi

On 29/05/2014 17:41, manning bill wrote:
> apparently there is not “enough consensus”, since several roots don’t have published v6 addresses.
> there -might- be rough consensus in a narrow slice of the technical community that has an axe to grind.
> end of the day, the IETF has no say on how people operate their networks/services.

I meant consensus here, not in the root server operator community.

I believe that there is a limit on the argument of operational
independence. If you agree to provide a service the whole Internet
depends on, well, it's reasonable that you need to comply with certain
requirements.

If an operator can't / won't comply with the requirements set by the
IETF, they can ask to be relieved of their duty.

> 
> if you think it should, i’d like to see a resolution of the DMARC deployment that requires all SMTP
> servers to require, per IETF mandate to support DMARC.
> 
> Engineering is not Operations.   This is not the IOTF.

DMARC/mailing lists are hardly critical infrastructure. This is not even
remotely comparable to the root server issue in terms of impact.

> 
> /bill

~Carlos
> Neca eos omnes.  Deus suos agnoscet.
> 
> On 29May2014Thursday, at 13:18, Carlos M. Martinez <carlosm3011@gmail.com> wrote:
> 
>> I think there is enough consensus saying that root server operators MUST
>> support IPv6. I think it's hard to argue that the Internet needs this to
>> move to IPv6, as otherwise we'll be saying that it'll be ok for future
>> networks to not be able to access some root servers, or putting the
>> burden of supporting all IPv6 on a subset of root servers.
>>
>> If you add that not all root server operators offer anycast copies, or
>> do it in a limited way, well, we could be putting the IPv6 internet in a
>> fragile position.
>>
>> IMO, setting this requirement is well within the core competencies of
>> the IETF.
>>
>> Then comes the question what to do (if anything) with those root server
>> operators who chose to ignore this MUST.
>>
>> IMO, This is probably outside the IETF's sphere, and it should be
>> possible to even say so in the proposed document.
>>
>> cheers!
>>
>> ~Carlos
>>
>> On 29/05/2014 05:24, Jari Arkko wrote:
>>>
>>>> I would like every A-M.root-servers.net have an A and AAAA record.
>>>>
>>>> I don't care how the root-server operators decide to partition to workload
>>>> among hardware.
>>>
>>> Yes, that is my view as well.
>>>
>>>> Over time we will need more v6 responders and fewer v4
>>>> responders.
>>>> I don't think that there is, or should be, any requirement that v4 and v6 be
>>>> answered by the same system, and given anycast, they might even be in
>>>> different locations.
>>>>
>>>> I think that the current text captures this just fine:
>>>
>>> Agreed.
>>>
>>> Jari
>>>
>>
>