
From nobody Fri Sep  1 12:39:19 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D10C132D5A for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 Dmo2O8eKsic4 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:39:16 -0700 (PDT)
Received: from mx18lb.world4you.com (mx18lb.world4you.com [81.19.149.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2799E1344B8 for <dnsop@ietf.org>; Fri,  1 Sep 2017 12:39:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=ggcSH7gj2pwxU7x9FszOPdsSEJHoAWGlyjkfTasiynk=;  b=w2fv/42WzpmAL9DSK4J1IR0KB0XXpzafHSw12DxBoa7Gg/v51eyZ4MDIhGozAzyMBYi5NFgcGDPnvMxlKliL0OGuxuBCBb/KkyrFfpQzBn/J+rVIkEGxTJOlpAuNL2z3FRhTUGJtE7QJy5LgEnXoI13ttY2JISX2lzgyiTjgDPk=;
Received: from [90.146.55.206] (helo=home.mail) by mx18lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1dnrmb-0001qD-Bx for dnsop@ietf.org; Fri, 01 Sep 2017 21:39:13 +0200
Message-ID: <59A9B760.2060209@mathemainzel.info>
Date: Fri, 01 Sep 2017 21:39:12 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com>
In-Reply-To: <150428805872.6417.9525310755360551475@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040409090800040607060602"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx18lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ww-FbSp3Nj6Oa4VWIEUcM62hnZM>
Subject: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 19:39:18 -0000

This is a cryptographically signed message in MIME format.

--------------ms040409090800040607060602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello,

in the draft
https://tools.ietf.org/html/draft-ietf-homenet-dot-14

I read this line

"The domain name 'home.arpa.' is to be used for naming within
residential homenets."

when this draft becomes an RFC - hopefully this year 2017 - then there=20
exists
an RFC, which gives you a domain name you can use in a home network/LAN
without conflicting to other things ..., the domain name 'home.arpa'

but there still doesn't exist any for company networks, they most=20
commonly use
the domain name 'local', which I already noticed, that this conflicts to =

RFC 6762 ...

Thanks,
Walter

>> On 01.09.2017 20:47, Ted Lemon wrote:
>>> On Sep 1, 2017, at 2:46 PM, Walter H. <Walter.H@mathemainzel.info> wr=
ote:
>>>> but there still doesn't exist any for company networks, they most co=
mmonly use
>>>> the domain name 'local', which I already noticed, that this conflict=
s to RFC 6762 ...
>>> That problem is not within the scope of the homenet working group to =
address.   You might consider raising it in the dnsop working group.
>

On 01.09.2017 19:47, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> This draft is a work item of the Home Networking WG of the IETF.
>
>          Title           : Special Use Domain 'home.arpa.'
>          Authors         : Pierre Pfister
>                            Ted Lemon
> 	Filename        : draft-ietf-homenet-dot-14.txt
> 	Pages           : 11
> 	Date            : 2017-09-01
>




--------------ms040409090800040607060602
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTAxMTkzOTEy
WjAjBgkqhkiG9w0BCQQxFgQUQeuUNFosORbnuF5GR9680HEqJGQwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAGwjPOwGV753+WSa
2e5ujkKzmQF1VaDmcmZNuWPLzL2EdVEx1FVX64dTlP5G6ojNd0ibCR5bUGet1BS+3WC8uIA9
LPn6sQ7XwDFb+Zalke1ZD7WIZ2dN4/TS62sboh+z43KyiwN+v3x0JHLizT44p6Pj3Au/pw4Y
6z2Siy76OD0kxoodjK1YkqU4cdCQnP4ZrcKz/GS89qtiOrorgJRjp/xfisC5fj5MQwDWAgG/
awU7/OsBXaIML2FcSVpNCX4dC4tNuHrLbxVmXIkoyuKnxF4fbNGGAyDnUxnJdNqwKgAqjo2X
oJj1+mOMR9F1WSMhE3IaoU9F/20edM+rJDrRh3cAAAAAAAA=
--------------ms040409090800040607060602--


From nobody Fri Sep  1 12:47:41 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F016D1330B1 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 KMtdVECQGONx for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:47:37 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2D3F132EE2 for <dnsop@ietf.org>; Fri,  1 Sep 2017 12:47:37 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:40190) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dnruh-000DNV-2x (Exim 4.89) (return-path <dot@dotat.at>); Fri, 01 Sep 2017 20:47:35 +0100
Date: Fri, 1 Sep 2017 20:47:35 +0100
From: Tony Finch <dot@dotat.at>
To: "Walter H." <Walter.H@mathemainzel.info>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <59A9B760.2060209@mathemainzel.info>
Message-ID: <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DNebLtGYO_Cmf00EyST8ShjVG0A>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 19:47:40 -0000

Walter H. <Walter.H@mathemainzel.info> wrote:
>
> but there still doesn't exist any for company networks,

The point of the homenet name is to provide a zero-configuration namespace
for consumer devices.

Corporate environments are a somewhat different matter, since you can
expect them to own their own domain name and have people who can set up
devices to use it. Internal networks should either use a subdomain of the
company's public domain, or register a second domain for internal use.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Fastnet: Variable becoming southwest 3 or 4, then backing south 5 or 6 later.
Slight or moderate, becoming rough later in west. Rain later. Good, becoming
moderate or poor later.


From nobody Fri Sep  1 12:58:35 2017
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BBC133085 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 j6KdYwaplmBR for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 12:58:32 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9893D133079 for <dnsop@ietf.org>; Fri,  1 Sep 2017 12:58:32 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xkVRS1DRGz21d; Fri,  1 Sep 2017 21:58:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504295908; bh=o/pTJNIHw/+5ZNQ8o/ay0cYAQcrUjGp2AwAkm29SMDA=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=VQm8CIMd0ZsPy7JB0Q9FIedKLnsFmkger0Z3uQs/FZU8VXPidUsZC6pItEC4kI/Ki dq1GjvM4dmHyvQxIZ5jbasPNOpj1h+AotwHdOmHU7cy9yQlOgGW+KW4VH8q9BkhMh1 b9jLKM38A/fKwUy0cIESovoV/S/3G3Uq1+KdSOXQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id wpCDB4w_CIV6; Fri,  1 Sep 2017 21:58:27 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri,  1 Sep 2017 21:58:27 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id D41FE96F; Fri,  1 Sep 2017 15:58:25 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D41FE96F
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id BC38840B8F46; Fri,  1 Sep 2017 15:58:25 -0400 (EDT)
Date: Fri, 1 Sep 2017 15:58:25 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: "Walter H." <Walter.H@mathemainzel.info>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <59A9B760.2060209@mathemainzel.info>
Message-ID: <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LDU0x0Ih7wHV4Zr-Rxhbq04rpkY>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 19:58:34 -0000

On Fri, 1 Sep 2017, Walter H. wrote:

> but there still doesn't exist any for company networks, they most commonly use
> the domain name 'local', which I already noticed, that this conflicts to RFC 6762 ...

If you are a company and you are using a hardcoded domain of "local",
then you have been and still are, completely broken. The only fix is to
rename your network.

I think you might be confused, and see "local" domain stuff on your
enterprise network, eg mdns stuff. That is its own realm.

Paul


From nobody Fri Sep  1 13:01:47 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97CA3134452 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 fNGIm0RSxJpm for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:01:43 -0700 (PDT)
Received: from mx01lb.world4you.com (mx01lb.world4you.com [81.19.149.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B26133147 for <dnsop@ietf.org>; Fri,  1 Sep 2017 13:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=QSc4xGyCcH599wPHNsHI6K6ae4lu/2HrjD5kKy+j3YI=;  b=a24GsEHn+4/aKgh1mBm3Cld/+RACH9Z09si9Knt9kelgkdEpbQYi8yT/EiPXZTOvu2V/DEayYwU84rWXEQFCpaBQXeKQKr9igizh6W3saQdPdJAA+u+HNgBWbRLDfx8Ep/975HzrNITE0Ka3PEvsTZmQavvcfE7kg77LYVprytM=;
Received: from [90.146.55.206] (helo=home.mail) by mx01lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1dns8L-0000Yw-EN; Fri, 01 Sep 2017 22:01:41 +0200
Message-ID: <59A9BCA2.6060008@mathemainzel.info>
Date: Fri, 01 Sep 2017 22:01:38 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010604000201070202040201"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx01lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5Oputuv5AzpLryWiTrGi3y_Xrnk>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 20:01:46 -0000

This is a cryptographically signed message in MIME format.

--------------ms010604000201070202040201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 01.09.2017 21:47, Tony Finch wrote:
> Walter H.<Walter.H@mathemainzel.info>  wrote:
>> but there still doesn't exist any for company networks,
> The point of the homenet name is to provide a zero-configuration namesp=
ace
> for consumer devices.
ACK
> Corporate environments are a somewhat different matter, since you can
> expect them to own their own domain name and have people who can set up=

> devices to use it.
BUT this need not necessarily be a public domain ..., just think of=20
Active Directory Domains ...
>   Internal networks should either use a subdomain of the
> company's public domain, or register a second domain for internal use.
>
such a registry where you can register domains for internal use doesn't=20
exist ...
not one registry is willing to give me a domain - even when I pay for=20
this - which I only use in a LAN,
and the authoritativ DNS servers would then just be  127.0.0.1 or ::1

there is a security reason why companies often use .local for this case=20
=2E.., but since RFC 6762 this conflicts ...
so there is the need of a TLD a company can use without conflicting ...


--------------ms010604000201070202040201
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTAxMjAwMTM4
WjAjBgkqhkiG9w0BCQQxFgQUM89YQnoSDzBnwS4sq/E7aNMfBvEwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAMp5h7tMTaZPj4pN
a8XGW+wRbu+kea3f4ZT+ySiKmNGQ5zJZ3nwkp8f0Y87Hn9AjyOMbD/tY6fiMrNHoSu3EmxQq
42mw+wbwxRSzhCS6JtKgsRI7UTxYYPhFLLb1nGPhfihD9kvBF/HIrwYG44Ga0mYUgyVK7vNt
sJk6jHXw9YsF//9t+XrIyKYWMV0u+XO8ku8GaChqbRYZcNaiVkN+OCSKKtZAAUApl3JqI+77
NazZT4P4xgZxcPlKR3c0XldesrusJiW/ZK5co/JgQer+RVJCC1I13nzV6yhQD+VLL3dBdpmr
3YH2gNuIQDWXHwmqfSoBzsUe75Uvo6eFMeSAw6wAAAAAAAA=
--------------ms010604000201070202040201--


From nobody Fri Sep  1 13:05:14 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2264134523 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 f8lDO9xsA1Lr for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:05:11 -0700 (PDT)
Received: from mx01lb.world4you.com (mx01lb.world4you.com [81.19.149.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADA7213441A for <dnsop@ietf.org>; Fri,  1 Sep 2017 13:05:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=RG00fy5pVKuPTxHqD9+rcRswWbZoioVkfzb6sudcB5Y=;  b=ZkRoVGl5boctbHHmXXlj5SnziFXeW4xuYKhmAMhjhuQQB6uyAZqFSlVWx92LO3AixNfy5NtBDmccTJ47vQCSDT28xjuUyp3+t8MMqQ71kwKxbMzCaP9O9JH8ta6bW+aObELkp5u5QIfAqiFAP+0KruFtE5KAcUdXV1t6SGsz6v0=;
Received: from [90.146.55.206] (helo=home.mail) by mx01lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1dnsBi-0001lA-8H; Fri, 01 Sep 2017 22:05:10 +0200
Message-ID: <59A9BD75.5010408@mathemainzel.info>
Date: Fri, 01 Sep 2017 22:05:09 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: Paul Wouters <paul@nohats.ca>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090604030908010100020807"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx01lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2K5t6fe7mxSsYOpc8Nhq0RYaMB0>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 20:05:13 -0000

This is a cryptographically signed message in MIME format.

--------------ms090604030908010100020807
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 01.09.2017 21:58, Paul Wouters wrote:
> On Fri, 1 Sep 2017, Walter H. wrote:
>
>> but there still doesn't exist any for company networks, they most=20
>> commonly use
>> the domain name 'local', which I already noticed, that this conflicts =

>> to RFC 6762 ...
>
> If you are a company and you are using a hardcoded domain of "local",
> then you have been and still are, completely broken. The only fix is to=

> rename your network.
ACK and which non public domain name I can use for this
    that doesn't conflict now and will not conflict in the future?



--------------ms090604030908010100020807
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTAxMjAwNTA5
WjAjBgkqhkiG9w0BCQQxFgQUbKg/swITpDyevYRHsBrbBy1ojbEwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAIcZPsp7Jm1PWkPL
JqcozpcBHEbMuLS/Xz6UgmWA9af1ZfmR397o8fRR3zBl9vJ5KPEDv9Yyxd3iRDylNNg/yfX4
z3nWjP8dM+M/9IgQqkniyMWC+k/hHEgRjH/Qn84s9aJQvlQeFvAgk9G39jvR4SwrBM0wOxFD
ROkoJ8T6IZDfQVhvfSmoLnV+fAbbY2gkJwU3+OyMEKtJicURQwpV+vkjv1d+lyQ8G/H/zgLR
DASyQV4oWKM1cXXPb3QnygtIJ1gTW+pFn1Kl2/JfT8SqlPfLLINHq6EoZTm3uSnknwJKwz49
bF4Xomg0hpW0il7vqe9JiQlqz6PWA4bhF3xrfAgAAAAAAAA=
--------------ms090604030908010100020807--


From nobody Fri Sep  1 13:06:40 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9491343DE for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 LbZLYpEMf1hB for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:06:36 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8B4E134233 for <dnsop@ietf.org>; Fri,  1 Sep 2017 13:06:36 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:40561) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dnsD5-000NeY-1T (Exim 4.89) (return-path <dot@dotat.at>); Fri, 01 Sep 2017 21:06:35 +0100
Date: Fri, 1 Sep 2017 21:06:35 +0100
From: Tony Finch <dot@dotat.at>
To: "Walter H." <Walter.H@mathemainzel.info>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <59A9BCA2.6060008@mathemainzel.info>
Message-ID: <alpine.DEB.2.11.1709012103070.2628@grey.csi.cam.ac.uk>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QdIHZfCpRTX8MgcMK5MCmqQh-NA>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 20:06:38 -0000

Walter H. <Walter.H@mathemainzel.info> wrote:

> such a registry where you can register domains for internal use doesn't
> exist ... not one registry is willing to give me a domain - even when I
> pay for this - which I only use in a LAN, and the authoritativ DNS
> servers would then just be 127.0.0.1 or ::1

You don't need to get funny with nameserver addresses. If you are using a
subdomain of your public domain you can just not serve the zone to the
public Internet (which is what we do for private.cam.ac.uk). If you are
using a second domain name, you can just host an empty zone somewhere
public, separate from the real internal zone.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Malin, Hebrides: West backing south 4 or 5, then backing southeast 5 to 7
later. Slight or moderate, becoming rough later in west. Rain later in west.
Mainly good.


From nobody Fri Sep  1 13:14:12 2017
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85AF81341DE for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 2gd9z9tG2fm4 for <dnsop@ietfa.amsl.com>; Fri,  1 Sep 2017 13:14:09 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21C151341B8 for <dnsop@ietf.org>; Fri,  1 Sep 2017 13:14:09 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xkVnR6CTxz21d; Fri,  1 Sep 2017 22:14:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504296843; bh=gX8bNpYtxhvbSGhaJRBTg1mh1hM8ckTwA4sc+ge8nZM=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=MWKW+YXaOUTh8QuUiXlpNeD88s6NmFERGN6H0JaYkx8NWhueIfhhIybTDqVwcCqvM TNfDAKvAx/t9Gk7C+WNw1cB9hp2B4QiInMdaJZUCQGSDHKn6FRpJEZyhV5VwgjxCoI Rtdv3bog0e1+KuxiyJZJTEQExbN6f0Xjdnf7gw1Q=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 37Uj5Ob8k6en; Fri,  1 Sep 2017 22:14:02 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri,  1 Sep 2017 22:14:02 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 4CF6296F; Fri,  1 Sep 2017 16:14:01 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 4CF6296F
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 394BB40B8F34; Fri,  1 Sep 2017 16:14:01 -0400 (EDT)
Date: Fri, 1 Sep 2017 16:14:01 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: "Walter H." <Walter.H@mathemainzel.info>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <59A9BD75.5010408@mathemainzel.info>
Message-ID: <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zB2uitJl2D1QOpgATCNYjuC8Xgk>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 20:14:10 -0000

On Fri, 1 Sep 2017, Walter H. wrote:

>> If you are a company and you are using a hardcoded domain of "local",
>> then you have been and still are, completely broken. The only fix is to
>> rename your network.
> ACK and which non public domain name I can use for this
>   that doesn't conflict now and will not conflict in the future?

Something that's yours and not squatted. For example internal.mathemainzel.info.

Please see the last three years of dnsops and homenet working group list
archives.

Paul


From nobody Sat Sep  2 17:30:09 2017
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18764132D0C for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 7mBDLStaLc_U for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:30:05 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F31E132F6B for <dnsop@ietf.org>; Sat,  2 Sep 2017 17:30:05 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id i145so3564118wmf.1 for <dnsop@ietf.org>; Sat, 02 Sep 2017 17:30:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RdbQReSwtjDiwSaYtPy4+l6BM9RFtjKtGVs6/tYUJac=; b=xxDvU0A0YGOEInwpXRZG7wYZw6eIRMw2eU3FzKuwrMCnD85F/2OpzbSo7Np75yr7DB c1eUvCOLKclxtY3XfBIuBRT1GMKr4ztT1puPdGspZeTbOs8Gu1o7kU7l5yfOAL5TQBkj DWBAGZsTsRlLaTdc3g350TYChUbKySPS6DfbVz7DzoXRVB5mGcDEmos7C18h2ctZDxYk ideEzZqtbvrQt1P0cy08CZcHzQeMgmNO3oiv6okgDJXZMlMu9v00Rf+UPA5+slZOvcPj aHIQkjIfVs15auG76CxVM1Ty6P3yX+xnPg1q3r7/BXrB0kAkfXXs3c7yafnMegZg4HDu dVCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RdbQReSwtjDiwSaYtPy4+l6BM9RFtjKtGVs6/tYUJac=; b=ckrB89S70ibWiO7PuCfSNmv7hfNF1L8boAiJI21h3qeiHdezran3mP1dJ4vP1nHdqP yZ6T524gVCuG9exwAmDOL/KoWYIYj+T4y8f3Rar7CzFbjVfJE2iAOa79kAef2Rqur+MU V5UyBeIZvFn4gR/ezFa/49ryD9BGo7ykKN2Jj8G++VnyhRM0MGSfELmiYtWeabwGOwlz gvp+yR/Grmzpjw3faO7Zm+PiCUjBvwo41RueckRwjn1um5LPOPunaGto8xnxEs+9lTV0 +gusvrJu5/mFAnTuqDI109XP/n5HxKSROe0HZ3LMRV0UmqZ6Sxxdin65T68Tburzf7KZ nrSg==
X-Gm-Message-State: AHPjjUgSRjtPQxgKZ0jI62SKdyK7axMkxcU3FXl3aw6e9KK4uTAK6Zf/ m1fUZtdfs+lxesuN9D82BotZZxG6WN/VTJQooA==
X-Google-Smtp-Source: ADKCNb5SmKBTnY9hPjUI+kfc6QkV4QvbID5E3/vwhc4fZYfKTN1gICjZKdcd5VLw40LU5iaA7bCkuDJP+liEWGFg2uM=
X-Received: by 10.28.101.132 with SMTP id z126mr1421118wmb.133.1504398603438;  Sat, 02 Sep 2017 17:30:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Sat, 2 Sep 2017 17:29:22 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca>
From: Warren Kumari <warren@kumari.net>
Date: Sat, 2 Sep 2017 20:29:22 -0400
Message-ID: <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Cc: "Walter H." <Walter.H@mathemainzel.info>, "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oRagp3bs5AcV2zBf8bt-2WSo17Y>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 00:30:07 -0000

On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters <paul@nohats.ca> wrote:
> On Fri, 1 Sep 2017, Walter H. wrote:
>
>>> If you are a company and you are using a hardcoded domain of "local",
>>> then you have been and still are, completely broken. The only fix is to
>>> rename your network.
>>
>> ACK and which non public domain name I can use for this
>>   that doesn't conflict now and will not conflict in the future?
>
>
> Something that's yours and not squatted. For example
> internal.mathemainzel.info.
>
> Please see the last three years of dnsops and homenet working group list
> archives.
>

... perhaps the other way of looking at the last thirty three years of
DNS is that people *do* actually want something like this, and that
perhaps it is time to actually create something specifically for it.
Our smacking people on the nose with rolled up newspapers and saying
"no, bad operator" ignores the fact that people still want this, and
still do this, and there ain't nothing we can do to stop them...

And so: https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00

This asks for a Special Use Name, specifically for this sort of thing
(and, yes, for building test networks, and for labeling devices which
have no Internet connection, etc). The desire and need for something
like this has been identified / discussed for a long time - the most
recent was probably when we decided that .alt would only be for
non-DNS contexts, and that someone should go make something like this
for the DNS - think of it like RFC1918 for names.
 It will require an unsecured delegation, for which we currently have
no process, and this (if people think it is a good idea!) will require
process to be created -- which A: will take many many years, and B: if
at least somewhat unlikely to happen -- but, if we don't at least ask,
we certainly won't get it...

And yes, this is somewhat of a straw-man.
W


>
> Paul
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Sat Sep  2 17:37:00 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCEA13300F for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jqMrFN8LzvCX for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:36:56 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08237132D0C for <dnsop@ietf.org>; Sat,  2 Sep 2017 17:36:56 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id v20so12718458qtg.3 for <dnsop@ietf.org>; Sat, 02 Sep 2017 17:36:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=sebeh1fxpvV4YiJPTHAfKkrCBKOZM4i1+iaPTw0VqNE=; b=HGwIJ6x9AmnGnSCl2VQHCMV30/yE/F2K+dOTqFuh3MAhbZZPzKzXQCUV/Qx8j5rU5j ZFXMyyx6aDZ3sFV3ICssPb8zMNCsbfnes43e0lTi5XqRx/YhgvWLCFSWmUmMjLJYdAvi Vy0th86lFcpilViJtL3lzphJVoGdPvIyka6c5mqLbxBw9YnF8CM2KbaT9Eg5MjkI9rb3 tZ1PIN4gYXASajDUSB9hIgbV+MdG/U0pVFiW9aA2DjXTxLt+7k0GQFOVl6FLjfIsibL+ v1dLhppLqdaAJYNz7hzgSYY7d2B4248HQ/a9RGIwgeKmKpY3pIjh8ciMqZ6PXAeTrOtm MJLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=sebeh1fxpvV4YiJPTHAfKkrCBKOZM4i1+iaPTw0VqNE=; b=JEkschnGav2O5nrQNDyf5iGgCtwlw8KLFvkqLpAe2Oza1d5t5SlOSrwGf4MkoWCIKr m4uHA/SZS4pPIbRpVQWYxzyehsQ0w2hRq1fJVleo0AsNd3lJCI9h/OvEsDWD0ye8I/jx NZVsPiOMLv8Ut+ERKW3caCdYwc3SzO9jyNyOV1n7tx3TX40Vvst+Th8xAVDacHRogyQb Y0pwuDvHoOMGFzS8HUv8KyA7fi0ht/qAIGAu/orUESRJccDMnRk/NWnF6CY64irxe4Am GEVRuo9Muw7rEiCqdy8mSFoszFKtoPdbFcE1hN8H7fAh0OQdorJmd/jHTEw8Kh9tP3U1 ggcQ==
X-Gm-Message-State: AHPjjUj5LQsX93vWyQ0IyDS17EkhTWhxHM1yMQkm11CB1rYMXQrTkt+R 3sksKeNTJfH/Xwhx7Io=
X-Google-Smtp-Source: ADKCNb75yKRChtf/sUOrNI1C2FDxaDjKOYJiY6GEzy+7M2UB+Zuqb/uDHW6QKpMEEzNZ4fJ+9sBTmw==
X-Received: by 10.200.52.34 with SMTP id u31mr10419212qtb.136.1504399015236; Sat, 02 Sep 2017 17:36:55 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:2447:13ef:7df7:c7f3? ([2601:18f:801:600:2447:13ef:7df7:c7f3]) by smtp.gmail.com with ESMTPSA id j129sm1593350qkd.92.2017.09.02.17.36.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Sep 2017 17:36:54 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Message-Id: <8462E244-3DD1-427A-A2D0-B51CFE1601C3@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6C6F236-7BFF-41B4-AC3B-6FFCA379463B"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 2 Sep 2017 20:36:50 -0400
In-Reply-To: <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org" <dnsop@ietf.org>, "Walter H." <Walter.H@mathemainzel.info>
To: Warren Kumari <warren@kumari.net>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/WRTpBjjjec1OxyuW21Eywhpw9y0>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 00:36:59 -0000

--Apple-Mail=_E6C6F236-7BFF-41B4-AC3B-6FFCA379463B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Sep 2, 2017, at 8:29 PM, Warren Kumari <warren@kumari.net> wrote:
>=20
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters <paul@nohats.ca> wrote:
>> On Fri, 1 Sep 2017, Walter H. wrote:
>>=20
>>>> If you are a company and you are using a hardcoded domain of =
"local",
>>>> then you have been and still are, completely broken. The only fix =
is to
>>>> rename your network.
>>>=20
>>> ACK and which non public domain name I can use for this
>>>  that doesn't conflict now and will not conflict in the future?
>>=20
>>=20
>> Something that's yours and not squatted. For example
>> internal.mathemainzel.info.
>>=20
>> Please see the last three years of dnsops and homenet working group =
list
>> archives.
>>=20
>=20
> ... perhaps the other way of looking at the last thirty three years of
> DNS is that people *do* actually want something like this, and that
> perhaps it is time to actually create something specifically for it.
> Our smacking people on the nose with rolled up newspapers and saying
> "no, bad operator" ignores the fact that people still want this, and
> still do this, and there ain't nothing we can do to stop them...
>=20
> And so: https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00
>=20
> This asks for a Special Use Name, specifically for this sort of thing
> (and, yes, for building test networks, and for labeling devices which
> have no Internet connection, etc). The desire and need for something
> like this has been identified / discussed for a long time - the most
> recent was probably when we decided that .alt would only be for
> non-DNS contexts, and that someone should go make something like this
> for the DNS - think of it like RFC1918 for names.
> It will require an unsecured delegation, for which we currently have
> no process, and this (if people think it is a good idea!) will require
> process to be created -- which A: will take many many years, and B: if
> at least somewhat unlikely to happen -- but, if we don't at least ask,
> we certainly won't get it...

Warren - I've only read part of your draft, and I'll comment on that =
part of it...

I was immediately struck by the parallel between <something-internal> =
and home.arpa.  How are the two cases different?  Can you explain why =
this text from section 3.2 of your doc applies to internal.arpa and not =
to homenet.arpa? =20

   It may also cause issues when server operators
   override part of the .arpa domain in order to instantiate
   something.arpa.

- Ralph


>=20
> And yes, this is somewhat of a straw-man.
> W
>=20
>=20
>>=20
>> Paul
>>=20
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
>=20
>=20
> --=20
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>   ---maf
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--Apple-Mail=_E6C6F236-7BFF-41B4-AC3B-6FFCA379463B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 2, 2017, at 8:29 PM, Warren Kumari &lt;<a =
href=3D"mailto:warren@kumari.net" class=3D"">warren@kumari.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters &lt;<a =
href=3D"mailto:paul@nohats.ca" class=3D"">paul@nohats.ca</a>&gt; =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">On Fri, 1 Sep =
2017, Walter H. wrote:<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite" class=3D"">If you are =
a company and you are using a hardcoded domain of "local",<br =
class=3D"">then you have been and still are, completely broken. The only =
fix is to<br class=3D"">rename your network.<br =
class=3D""></blockquote><br class=3D"">ACK and which non public domain =
name I can use for this<br class=3D""> &nbsp;that doesn't conflict now =
and will not conflict in the future?<br class=3D""></blockquote><br =
class=3D""><br class=3D"">Something that's yours and not squatted. For =
example<br class=3D""><a href=3D"http://internal.mathemainzel.info" =
class=3D"">internal.mathemainzel.info</a>.<br class=3D""><br =
class=3D"">Please see the last three years of dnsops and homenet working =
group list<br class=3D"">archives.<br class=3D""><br =
class=3D""></blockquote><br class=3D"">... perhaps the other way of =
looking at the last thirty three years of<br class=3D"">DNS is that =
people *do* actually want something like this, and that<br =
class=3D"">perhaps it is time to actually create something specifically =
for it.<br class=3D"">Our smacking people on the nose with rolled up =
newspapers and saying<br class=3D"">"no, bad operator" ignores the fact =
that people still want this, and<br class=3D"">still do this, and there =
ain't nothing we can do to stop them...<br class=3D""><br class=3D"">And =
so: <a =
href=3D"https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00" =
class=3D"">https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00</a>=
<br class=3D""><br class=3D"">This asks for a Special Use Name, =
specifically for this sort of thing<br class=3D"">(and, yes, for =
building test networks, and for labeling devices which<br class=3D"">have =
no Internet connection, etc). The desire and need for something<br =
class=3D"">like this has been identified / discussed for a long time - =
the most<br class=3D"">recent was probably when we decided that .alt =
would only be for<br class=3D"">non-DNS contexts, and that someone =
should go make something like this<br class=3D"">for the DNS - think of =
it like RFC1918 for names.<br class=3D""> It will require an unsecured =
delegation, for which we currently have<br class=3D"">no process, and =
this (if people think it is a good idea!) will require<br =
class=3D"">process to be created -- which A: will take many many years, =
and B: if<br class=3D"">at least somewhat unlikely to happen -- but, if =
we don't at least ask,<br class=3D"">we certainly won't get it...<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Warren - =
I've only read part of your draft, and I'll comment on that part of =
it...</div><div><br class=3D""></div><div>I was immediately struck by =
the parallel between &lt;something-internal&gt; and home.arpa. &nbsp;How =
are the two cases different? &nbsp;Can you explain why this text from =
section 3.2 of your doc applies to internal.arpa and not to =
homenet.arpa? &nbsp;</div><div><br class=3D""></div><div><pre =
class=3D"newpage" style=3D"font-size: 13.333333015441895px; margin-top: =
0px; margin-bottom: 0px; break-before: page;">   It may also cause =
issues when server operators
   override part of the .arpa domain in order to instantiate
   something.arpa.</pre><pre class=3D"newpage" style=3D"font-size: =
13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: =
page;"><br class=3D""></pre><pre class=3D"newpage" style=3D"font-size: =
13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: =
page;">- Ralph</pre><pre class=3D"newpage" style=3D"font-size: =
13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: =
page;"><br class=3D""></pre><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">And yes, this is somewhat of a straw-man.<br =
class=3D"">W<br class=3D""><br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"">Paul<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">DNSOP mailing list<br class=3D""><a =
href=3D"mailto:DNSOP@ietf.org" class=3D"">DNSOP@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/dnsop<br =
class=3D""></blockquote><br class=3D""><br class=3D""><br class=3D"">-- =
<br class=3D"">I don't think the execution is relevant when it was =
obviously a bad<br class=3D"">idea in the first place.<br class=3D"">This =
is like putting rabid weasels in your pants, and later expressing<br =
class=3D"">regret at having chosen those particular rabid weasels and =
that pair<br class=3D"">of pants.<br class=3D""> &nbsp;&nbsp;---maf<br =
class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">DNSOP mailing list<br class=3D""><a =
href=3D"mailto:DNSOP@ietf.org" class=3D"">DNSOP@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/dnsop<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_E6C6F236-7BFF-41B4-AC3B-6FFCA379463B--


From nobody Sat Sep  2 17:55:17 2017
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7822D132E17 for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 jq2cuMucebVl for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 17:55:14 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F29132937 for <dnsop@ietf.org>; Sat,  2 Sep 2017 17:55:14 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id v2so17924873wmf.0 for <dnsop@ietf.org>; Sat, 02 Sep 2017 17:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2znevA851ARPZCME2r4Nd+akfXj8t5z64ZNg2AaxITA=; b=hFWKdU7jtHISiZHsnP+VAiA5UsKHQdBiUM/gbwaOVVmUKE4d5/IaCQAxH3FhA6FgGG o/cFUnLclXNPQKABBvbm0RySl12oOHtfguLrMc8utz2gIX+oygzftsnJfjtDhYZDbv6J WGBgt2VfGSCBowHNibljp17Pq0oy2ScEb8dnee6VZXlHyljaIfUyL9bu8axyI0HZMelP cCqCkBcXaY58q2QmSLvmgOGtQBQIsu6kcjHa1r+gdzf2VDIPgGaXc173SRXJRDEb4zXL NsrBFm9OLq/PV6gvLm23Yq0yP6hjMIe4WxfBJAOl/yB0IA2zO14tHglH2zxLyGxfDhRa z3mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2znevA851ARPZCME2r4Nd+akfXj8t5z64ZNg2AaxITA=; b=FwkdUrLgKlhcMNqN0DiYBP6UAjUr59tOd9qB5k8FhE/j7ESaIuKfy/RguoA7uJtvQG beN0kcEsD4+tFgmiUjp6Wwcpi/IVflaN3ve5aNtPC7IjV2oCRh/Eqs6tzbnVYfQkHopK v4eYu/scva4972RKy3FXErr8t6LmVRvnVv05BZqvgbj+wGCpVO/xQS942ihwaVLBp1xX kkaWX9djSgawQ/ZNzED94AGUPL420hwT8nfbpT2uHIizJyP1Jq4FI8pEFacRT1vr8FW+ J0XAD4w97ktCOJy4n2gGNudKUsMPj5fGsAnsQe+6vus2SGXKwMA0fx3iMpiNCseal5mF MOZQ==
X-Gm-Message-State: AHPjjUhRW2iqAv7RAsdavO6+dOthnP5zrk7zMu0ZgepLtOZq6pS16Peh hRJEuTWEHqMfDvcTa9g0RcXfFufl4Vjc
X-Google-Smtp-Source: ADKCNb7t5HEisabdPd0Nm0o1yr9eqRNSxDH37VJrs4rZr8PQA7dD1O6398ETYyfvCeFdEVQIB0o/EX6BEyq4LlYPL0g=
X-Received: by 10.28.175.76 with SMTP id y73mr1665467wme.33.1504400112473; Sat, 02 Sep 2017 17:55:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Sat, 2 Sep 2017 17:54:31 -0700 (PDT)
In-Reply-To: <8462E244-3DD1-427A-A2D0-B51CFE1601C3@gmail.com>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com> <8462E244-3DD1-427A-A2D0-B51CFE1601C3@gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Sat, 2 Sep 2017 20:54:31 -0400
Message-ID: <CAHw9_iJBW8FUVeT18rfxFTBYRVUCAMEyezxcGzhc4szn+Q9Z=Q@mail.gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org" <dnsop@ietf.org>,  "Walter H." <Walter.H@mathemainzel.info>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zMxgWoJMzRHeVjiKXtLbedRjmu8>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 00:55:16 -0000

On Sat, Sep 2, 2017 at 8:36 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> On Sep 2, 2017, at 8:29 PM, Warren Kumari <warren@kumari.net> wrote:
>
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters <paul@nohats.ca> wrote:
>
> On Fri, 1 Sep 2017, Walter H. wrote:
>
> If you are a company and you are using a hardcoded domain of "local",
> then you have been and still are, completely broken. The only fix is to
> rename your network.
>
>
> ACK and which non public domain name I can use for this
>  that doesn't conflict now and will not conflict in the future?
>
>
>
> Something that's yours and not squatted. For example
> internal.mathemainzel.info.
>
> Please see the last three years of dnsops and homenet working group list
> archives.
>
>
> ... perhaps the other way of looking at the last thirty three years of
> DNS is that people *do* actually want something like this, and that
> perhaps it is time to actually create something specifically for it.
> Our smacking people on the nose with rolled up newspapers and saying
> "no, bad operator" ignores the fact that people still want this, and
> still do this, and there ain't nothing we can do to stop them...
>
> And so: https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00
>
> This asks for a Special Use Name, specifically for this sort of thing
> (and, yes, for building test networks, and for labeling devices which
> have no Internet connection, etc). The desire and need for something
> like this has been identified / discussed for a long time - the most
> recent was probably when we decided that .alt would only be for
> non-DNS contexts, and that someone should go make something like this
> for the DNS - think of it like RFC1918 for names.
> It will require an unsecured delegation, for which we currently have
> no process, and this (if people think it is a good idea!) will require
> process to be created -- which A: will take many many years, and B: if
> at least somewhat unlikely to happen -- but, if we don't at least ask,
> we certainly won't get it...
>
>
> Warren - I've only read part of your draft, and I'll comment on that part of
> it...
>
> I was immediately struck by the parallel between <something-internal> and
> home.arpa.  How are the two cases different?  Can you explain why this text
> from section 3.2 of your doc applies to internal.arpa and not to
> homenet.arpa?

Honestly, not really. Well, more fully, I don't have a very concrete
answer, but I *do* have a lot of handwaving if you'd like?

This text made me uncomfortable when I wrote it, for a number of
reasons. Firstly, I am somewhat concerned that some set of people will
manage to break arpa when they put in magic for home.arpa, but I also
feel that the deployments scenarios are likely to be somewhat
different - for home.arpa I'm assuming that this will be added to
name-server distributions, and the names that *do* exist will be
automatically created, and answered from homenet devices. If there
were an "internal.arpa", I'm assuming that it would be much more
likely that some admin behind a keyboard will be editing zonefiles and
fiddling with the config, and so more likely to break it.

As I said, this is a very hand-wavey argument, fully divorced from
rigor. But, whatever the case, much of the purpose of this is for
internal namespaces, where users will be seeing and interacting with
the names (and not using automated UIs) -- and so I think that
internal.arpa fails the "does this look nice" test (which is also
hand-wavey :-))

W



>
>    It may also cause issues when server operators
>    override part of the .arpa domain in order to instantiate
>    something.arpa.
>


>
> - Ralph
>
>
>
>
> And yes, this is somewhat of a straw-man.
> W
>
>
>
> Paul
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>   ---maf
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Sat Sep  2 19:23:35 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4677D1329C8 for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 19:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Hht-XfnvoYrj for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 19:23:31 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D00E41321C9 for <dnsop@ietf.org>; Sat,  2 Sep 2017 19:23:31 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:104a:9f00:a4be:7005] (unknown [IPv6:2001:559:8000:c9:104a:9f00:a4be:7005]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 7AF1C61FF3; Sun,  3 Sep 2017 02:23:30 +0000 (UTC)
Message-ID: <59AB67A2.3000008@redbarn.org>
Date: Sat, 02 Sep 2017 19:23:30 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
CC: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org" <dnsop@ietf.org>,  "Walter H." <Walter.H@mathemainzel.info>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
In-Reply-To: <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZUeYmVJqjz_AjblWMZ6ePJCCX_k>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 02:23:33 -0000

Warren Kumari wrote:
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters<paul@nohats.ca>  wrote:
>> Please see the last three years of dnsops and homenet working group list
>> archives.
>>
>
> ... perhaps the other way of looking at the last thirty three years of
> DNS is that people *do* actually want something like this, and that
> perhaps it is time to actually create something specifically for it.

i think what people want is bigger than this, and that as a part, this 
part is small. one of the big differences between internet and its early 
competitors such as appletalk or decnet or the rest is that while the 
networks that died so that the internet could live did not scale -- they 
worked in a building or a network or a campus or a corporation, but not 
globally. whereas the internet works globally, but not locally.

we do not have well defined automation for making local names work when 
the internet connection is down. at a very modest level of necessary and 
inevitable complexity, one's own in-perimeter recursive servers can't 
find one's own in-perimeter authority servers. so if your internet 
connection goes down, then way more stuff becomes effectively 
unreachable than what's on the far side of the disconnection point.

mark andrews faced disconnections of this kind as a daily part of his 
work about 30 years ago when he developed the "stub zone" feature and 
contributed it to BIND4. but we have yet to automate it. and this rat 
hole is a deep one, because sometimes the disconnection is "all the 
links connecting my city / state / island / country to the rest of the 
global internet" and sometimes it's just your laptop, or one vm, or your 
LAN, or your house or office or campus.

in other words the necessary automation isn't going to benefit from 
static hints. it's a pity we can't rely on multicast for this kind of 
thing, although that often will work at the campus level.

in any case what "people *do* actually want" here is that naming always 
works for the devices and services one can reach and wishes to reach by 
name, for a network of arbitrary diameter, from a single container all 
the way up to interplanetary scope.

figuring out what names to reserve for which magnitude of diameter is a 
fool's errand, and so i've been ignoring homenet and all of its DNS 
related work.

we've been making people edit a "hosts" file for local naming and that's 
crazy. apple did something slightly more marketable by using multicast 
but that doesn't scale either. we've been making rfc1918 networks run a 
fake root zone that contains delegations to local servers. this is all 
wrongthink. it's not what the internet should be or how it should feel 
to use. we have PnP for devices now, but hardly for networks, unless all 
of the devices on the network come from apple, and none of them are 
outside the local (corporate? campus?) multicast domain.

DNS was a necessary first step and we took it. but we've known for at 
least the last 25 years that its architecture was too rigid when it 
comes to reachability by packet or of naming systems. if it's time to 
think about what people actually want to be doing, let's start there.

> Our smacking people on the nose with rolled up newspapers and saying
> "no, bad operator" ignores the fact that people still want this, and
> still do this, and there ain't nothing we can do to stop them...
>
> And so: https://tools.ietf.org/html/draft-wkumari-dnsop-internal-00

...not here.

-- 
P Vixie


From nobody Sat Sep  2 21:32:07 2017
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3908F132925 for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 21:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 TAgpxaufa-1m for <dnsop@ietfa.amsl.com>; Sat,  2 Sep 2017 21:32:04 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [192.36.115.55]) by ietfa.amsl.com (Postfix) with ESMTP id 79C1B1328DB for <dnsop@ietf.org>; Sat,  2 Sep 2017 21:32:04 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id A66F39E40; Sun,  3 Sep 2017 06:32:02 +0200 (CEST)
Date: Sun, 3 Sep 2017 06:32:02 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: "Walter H." <Walter.H@mathemainzel.info>
Cc: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20170903043202.GA18082@besserwisser.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1"
Content-Disposition: inline
In-Reply-To: <59A9BCA2.6060008@mathemainzel.info>
X-URL: http://vvv.besserwisser.org
X-Clacks-Overhead: "GNU Sir Terry Pratchett"
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/spmrgo3L8enj4r8JRV3V_zySHas>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 04:32:06 -0000

--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: [DNSOP] DNS names for local networks - not only home residenta=
l networks ... Date: Fri, Sep 01, 2017 at 10:01:38PM +0200 Quoting Walter H=
=2E (Walter.H@mathemainzel.info):
> On 01.09.2017 21:47, Tony Finch wrote:

> > Corporate environments are a somewhat different matter, since you can
> > expect them to own their own domain name and have people who can set up
> > devices to use it.
> BUT this need not necessarily be a public domain ..., just think of Active
> Directory Domains ...

AD is DNS, and it follows the same rules. A sub-domain, a separate domain
or two-face (using the same domain name as you public-facing resources
but a different set of authoritative servers and some careful setup of
full-service resolvers), all work. The single thing that does not work
is to use name-space you do not own (like LOCAL or a domain name from a
non-existent TLD, like "web". Ooops. It does now...) and hope it doesn't
escape. Or that somebody registers the name and tries to impersonate you.

I've run two-face, and the results were excellent. But watch out with
DNSSEC; you need to have the same keys signing both zones.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE           SA0XLR            +46 705 989668
Our father who art in heaven ... I sincerely pray that SOMEBODY at this
table will PAY for my SHREDDED WHAT and ENGLISH MUFFIN ... and also
leave a GENEROUS TIP ....

--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJZq4XCAAoJEA4LceDT9hu0JeAP/1KY4G+SfVR93RROngx5rDBw
xXBE6GWMFeWKd0IFtxRPUc5ai2AI/p0pyrb2RVKxLSLHG4AwjESdA1R/us/Gsg3S
/JCz2tpRF+JSisbyztN4JCCyIQdo/70ognDuNOmkIT1KZbg5y8fBoEkz88FcdN9H
EjmK4RJUoGEP0WZ5P8/D6JSo7wV7c1XiyXqVOSKTENogiyxq607U9Q4fElY5xh3p
lf7RCuLZrkmQx0AU/NAB+l00jKRO4q7SyYNgWQHRsWkBu+tLALi/AbitHUckWedM
iYVi5kmUnjQMR5nlBJp+ypmG40lnkKCEtBUB6Ie6QK6HqqSmFAiXoHGoWneHBYSV
+YvsI1muyssdsVFGCCZhlZ9tsqxYVT7L8DA4x+JIN+GlvLACv/DdEO8CiaYimcWM
WUAYDGSLs0FiraV1DvgX3TRka/Gek3+vQQPchXro+zuFctYiDiFNFvIl4fxknbER
B1//31zub2o+il9xLfLeGVUHO+vyCZvBZON7c45N8C+pmBNs4nmSlkl1Q0rFXPO3
2WWTYv98458DV8QxMxNpLm19mR6ucHqQkwbXfhpzkHnTY7P80OLDw2u/M7I+V6G5
MLBwMj7aZkvR2QbxprsAeJmGCVul4bxjBjWE91j5bTHZRXCV5wjpYw9bTSeQThHH
ZjDTsuvK0F2RUlpkX7gB
=4Oar
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--


From nobody Sun Sep  3 00:21:29 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1EFD12421A for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 00:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=XVWxXNOU; dkim=pass (1024-bit key) header.d=yitter.info header.b=JVB5En33
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 bR_FzjWKOtjd for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 00:21:25 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 647EF12ECEC for <dnsop@ietf.org>; Sun,  3 Sep 2017 00:21:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id C83E6BEA1E for <dnsop@ietf.org>; Sun,  3 Sep 2017 07:21:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504423281; bh=cPlpG5/qI3dQXR4K8/2/eZCaLXHwNrysq2coi689nFw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=XVWxXNOUdSmanGy0iFcytL5b28LSQALyX5t9v5YPDfgZ3d/k63V92fXnPdUHBN0WQ LDpEZQLPyoyav6YeaAD51oFkazaJ2528USYSYb2Zt0x026Q03U4tvO9t6QJZ40Ch6p CZkv7RAShhvvfqxaAOM4GZqR/BF0Qs/ke71mD62Q=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VuO-fAfxL12 for <dnsop@ietf.org>; Sun,  3 Sep 2017 07:21:15 +0000 (UTC)
Date: Sun, 3 Sep 2017 03:21:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504423275; bh=cPlpG5/qI3dQXR4K8/2/eZCaLXHwNrysq2coi689nFw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=JVB5En33bgBuwf26GsldWqkmt4LGd5nuqduP0Q/kPwVrvlyJpV51j1lKa8vnHB4rh KSOp6JgNgQCScA5k12V69A53OtsOrP+W9I6ISz9iDj0lLe0d6j5TKB3+BNU1ctSO4Q /Vm7RgZ88tek6pEPNfjiyRtbNKKyvROocK2UGqtU=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170903072119.s2q43ejytoofdx3x@mx4.yitter.info>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59A9BCA2.6060008@mathemainzel.info>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ezMv4v6FGOMDGjTgrMPSaPc4qVI>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 07:21:27 -0000

Hi,

On Fri, Sep 01, 2017 at 10:01:38PM +0200, Walter H. wrote:
> >   Internal networks should either use a subdomain of the
> > company's public domain, or register a second domain for internal use.
> > 
> such a registry where you can register domains for internal use doesn't
> exist ...
> not one registry is willing to give me a domain - even when I pay for this -
> which I only use in a LAN,
> and the authoritativ DNS servers would then just be  127.0.0.1 or ::1

I respectfully disagree.  You could register any domain you like today
and fence it off just as effectively as you might wish.  Please
provide an example where you cannot.

> there is a security reason why companies often use .local for this case ...,

Any company that uses .local for any security reasons is one that I
want as my competitor.  I'd love to know the names of such companies!

Best regards,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Sun Sep  3 11:47:42 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF84213234E for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 11:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 AGEIqdl0Wm_h for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 11:47:37 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC6A8132351 for <dnsop@ietf.org>; Sun,  3 Sep 2017 11:47:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=QxdeYmZDfAt+LItMwj0DFDwwvHvRsdTD8jXbNKhI+8A=;  b=lorrTtZFwCAjIQ0PY97/sFIKBHddH7n4YH6UA7QzNkdo/GH88j3QMYT9mUUJiP4MLFrRVmNbdarC8T0oi7aNNlnPEYcq335dupL5JJDWGDp0+TXmdZAoTW5Bus+A1yvmsuW+5WxFkJv25DUyK5YU4slUoXPVjRmafb/0GEQR32U=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1doZvg-0001Xr-ML; Sun, 03 Sep 2017 20:47:32 +0200
Message-ID: <59AC4E42.9080600@mathemainzel.info>
Date: Sun, 03 Sep 2017 20:47:30 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: =?UTF-8?B?TcOlbnMgTmlsc3Nvbg==?= <mansaxel@besserwisser.org>
CC: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org>
In-Reply-To: <20170903043202.GA18082@besserwisser.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010503000509090806050804"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ffafaduHsddW59sbJKjlarBVHOs>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 18:47:41 -0000

This is a cryptographically signed message in MIME format.

--------------ms010503000509090806050804
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 03.09.2017 06:32, M=C3=A5ns Nilsson wrote:
> Corporate environments are a somewhat different matter, since you can
> expect them to own their own domain name and have people who can set up=

> devices to use it.
>> BUT this need not necessarily be a public domain ..., just think of Ac=
tive
>> Directory Domains ...
> AD is DNS, and it follows the same rules.
yes and no; AD is more, and so many companies got the advice to use a=20
domain name,
that is NOT public, because it is not internet ...
>   A sub-domain, a separate domain
> or two-face (using the same domain name as you public-facing resources
> but a different set of authoritative servers and some careful setup of
> full-service resolvers), all work. The single thing that does not work
> is to use name-space you do not own (like LOCAL or a domain name from a=

> non-existent TLD, like "web". Ooops. It does now...) and hope it doesn'=
t
> escape. Or that somebody registers the name and tries to impersonate yo=
u.
even if I fully ACK this, but 15 years ago, nobody said, that  ".local", =

=2E.. would conflict one day ...
and also the company I work for has decided at these times to use a=20
".local" as internal domain and AD;
now it is impossible to change this ...

I for myself use a ".home.arpa" as internal name (I'm no company just a=20
citizen),
and for IPv6 connections I use a subdomain of my public domain,
which is only used to get resolved correctly ...
e.g.  the IPv6 of my proxy resolves to  proxy.sub.example.com and=20
proxy.sub.example.com resolved to this IPv6 ...
and router (firewall) blocks the whole prefix to be connected from=20
outside (internet) ...

Greetings,
Walter


--------------ms010503000509090806050804
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTAzMTg0NzMw
WjAjBgkqhkiG9w0BCQQxFgQUeq3s0DlMZhfahFlRnYNrrAc7hnQwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAFSIfNWryq+VO78o
8LBi5miHfgMMBBwyG2H+io6H1fmDXbAmvYORVB/muYWNjqe9ZdYohwK+B07wVdi7zE6AOY5T
gFqmX8cw5CqfozZCUeKVvk8pmnbrC+vFlEDMFlGHWmv+3Sl5k2Rf44WoMDjI1kSda9AayV/2
clLq99bK8itKqYO6wnLrHo22s3C6McMQYXMJHjoCc9tvqbS9BnSL8Ed6aQm7fANZLJWezvAw
00B8qtxr51SN+ZcAHUvkrZ+STeYp5GdBpTAl1dNIjtRxBNA5+PZCqlSN947C6ZGTBh62HMtx
j8tQ1lw05cR7SWyfXy7yXd1OzzDPNcAu278oyJUAAAAAAAA=
--------------ms010503000509090806050804--


From nobody Sun Sep  3 12:07:29 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01E613234E for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 12:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 89SsoYd_iNNz for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 12:07:25 -0700 (PDT)
Received: from mx06lb.world4you.com (mx06lb.world4you.com [81.19.149.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2CE7132355 for <dnsop@ietf.org>; Sun,  3 Sep 2017 12:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=QqpPtLT4EcotRhyFIa03BkPaLdFknuG4KcvzvJdY7qU=;  b=VkMwV7wfWlYeUGh+l1Jo0tmHvQfrA4bouOnmEL6O0q64o2BwVHnpDJcnY79l4475q/iX0eqIxwxtomwqQRFg8TSlsZr94O0apCa7irYAYM7Lb+nbMkcnI+ONeKCrBzj33Tb91pmmZ+jJPZlOifVeF3l8aWPAK8XQFnD7xRdrq/w=;
Received: from [90.146.55.206] (helo=home.mail) by mx06lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1doaEs-0000yW-Qw; Sun, 03 Sep 2017 21:07:22 +0200
Message-ID: <59AC52EA.7060403@mathemainzel.info>
Date: Sun, 03 Sep 2017 21:07:22 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
CC: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
In-Reply-To: <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010209080304060509080500"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx06lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6EiHfcHHcN-B_Rjtyjma6zGrR-c>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 19:07:27 -0000

This is a cryptographically signed message in MIME format.

--------------ms010209080304060509080500
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 03.09.2017 02:29, Warren Kumari wrote:
> On Fri, Sep 1, 2017 at 4:14 PM, Paul Wouters<paul@nohats.ca>  wrote:
>> On Fri, 1 Sep 2017, Walter H. wrote:
>>
>>>> If you are a company and you are using a hardcoded domain of "local"=
,
>>>> then you have been and still are, completely broken. The only fix is=
 to
>>>> rename your network.
>>> ACK and which non public domain name I can use for this
>>>    that doesn't conflict now and will not conflict in the future?
>>
>> Something that's yours and not squatted. For example
>> internal.mathemainzel.info.
>>
>> Please see the last three years of dnsops and homenet working group li=
st
>> archives.
>>
> ... perhaps the other way of looking at the last thirty three years of
> DNS is that people *do* actually want something like this, and that
> perhaps it is time to actually create something specifically for it.
just a simple question: why hadn't there been such at the very beginning,=

which could have prevented situations like the following:

"a company gets the advice to use a ".local" as the internal domain and=20
Active Directory;
at these times nobody would have thought, that this could be a=20
conflicting problem in the future ...;
and now it is impossible to change this ..."

now telling an admin not to use ".local" is easy, but 15 years ago ...


--------------ms010209080304060509080500
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTAzMTkwNzIy
WjAjBgkqhkiG9w0BCQQxFgQUDd47V+Ryp8AvZppeBwfZ221fv6kwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBABM0pB7Rz39RMxCQ
YDP9y7Cf0i+kUzKQYSnYjwxYbCFJVT1EuJUPYFsQuJBxegEXy2pcoA1kIfBumk1b5o4KIaUe
ij06jPNrxk+uDzPnZaHngj6XpqC/QtyyZY9CCiOgm96oIZn8v/uEdkCjXwvuDP2jk9bxN9CF
zzmhSGx3l8TmfWInLXJRXVqAwDc2iAPchGKRKPL5eJhJCb1pMvO3hG+00T8uy5NQujin42oo
20oNFs43T5s6apBDmGkew6V79LG/rivM76oywJp3sCFn9aDETuhS474ntWVmDagmPoI/kPUJ
KKpxjJIqVvnyohqsuiRK36JiPeI/6HE8rN5plXgAAAAAAAA=
--------------ms010209080304060509080500--


From nobody Sun Sep  3 14:38:56 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD3813233D for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 14:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 UV3uznulFKrs for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 14:38:52 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C00241241F3 for <dnsop@ietf.org>; Sun,  3 Sep 2017 14:38:52 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 11E8D24AE19; Sun,  3 Sep 2017 21:38:37 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9DB3C160041; Sun,  3 Sep 2017 21:38:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8CA7216007E; Sun,  3 Sep 2017 21:38:43 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dBF28Ns-x9Kx; Sun,  3 Sep 2017 21:38:43 +0000 (UTC)
Received: from [172.30.42.89] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id DB3CD160041; Sun,  3 Sep 2017 21:38:42 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <59AC4E42.9080600@mathemainzel.info>
Date: Mon, 4 Sep 2017 07:38:53 +1000
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info>
To: "Walter H." <Walter.H@mathemainzel.info>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/fDNSrL34vPA2FEqbLcMJUsZAloQ>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 21:38:54 -0000

> ]On 4 Sep 2017, at 4:47 am, Walter H. <Walter.H@mathemainzel.info> =
wrote:
>=20
> even if I fully ACK this, but 15 years ago, nobody said, that  =
".local", ... would conflict one day ...
> and also the company I work for has decided at these times to use a =
".local" as internal domain and AD;
> now it is impossible to change this ...

Why would anyone tell you that =E2=80=9C.local=E2=80=9D would conflict =
when you were supposed
to register a name *before* using it.  That=E2=80=99s been the case =
since the very beginning.
No one ever said there would not be new TLD=E2=80=99s registered.  You =
gambled and you
lost.

If you are doing AD correctly you should be able to register you =
machines wherever
they connect to the Internet and that requires a public registration.

Mark
--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Sun Sep  3 14:51:57 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B3B132397 for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 14:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 F4seryKT-rmJ for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 14:51:55 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40793126B71 for <dnsop@ietf.org>; Sun,  3 Sep 2017 14:51:55 -0700 (PDT)
Received: from [10.32.60.52] (50-1-98-42.dsl.dynamic.fusionbroadband.com [50.1.98.42]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v83LomjS075447 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Sep 2017 14:50:49 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-42.dsl.dynamic.fusionbroadband.com [50.1.98.42] claimed to be [10.32.60.52]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Mark Andrews" <marka@isc.org>, "Walter H." <Walter.H@mathemainzel.info>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Date: Sun, 03 Sep 2017 14:51:51 -0700
Message-ID: <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org>
In-Reply-To: <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YLqsawzQaOnE_cdm6FhNY3uaboQ>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Sep 2017 21:51:56 -0000

On 3 Sep 2017, at 14:38, Mark Andrews wrote:

>> ]On 4 Sep 2017, at 4:47 am, Walter H. <Walter.H@mathemainzel.info> 
>> wrote:
>>
>> even if I fully ACK this, but 15 years ago, nobody said, that  
>> ".local", ... would conflict one day ...
>> and also the company I work for has decided at these times to use a 
>> ".local" as internal domain and AD;
>> now it is impossible to change this ...
>
> Why would anyone tell you that “.local” would conflict when you 
> were supposed
> to register a name *before* using it.

Because some vendors gave bad advice in their documentation, 
particularly in examples.

> That’s been the case since the very beginning.
> No one ever said there would not be new TLD’s registered.  You 
> gambled and you
> lost.

If an end-user follows advice from vendors, and the vendors turn out to 
be wrong, maybe statements like that are inappropriate.

> If you are doing AD correctly you should be able to register you 
> machines wherever
> they connect to the Internet and that requires a public registration.

And that is what Microsoft has suggested in all their documentation for 
many years.

--Paul Hoffman


From nobody Sun Sep  3 22:56:53 2017
Return-Path: <sca@andreasschulze.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B501243F6 for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 22:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level: 
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=andreasschulze.de
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 vdGdLtM_Qq3G for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 22:56:49 -0700 (PDT)
Received: from mail.somaf.de (mail.somaf.de [IPv6:2001:470:77b3:100::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AFC8124239 for <dnsop@ietf.org>; Sun,  3 Sep 2017 22:56:49 -0700 (PDT)
Date: Mon, 04 Sep 2017 07:56:44 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=andreasschulze.de; s=ybz; t=1504504605; bh=1Gn1OdH0gslSzqxgRwYK7l1V+wVtbpQ2D3I7Te2r6UQ=; h=Date:From:To:Subject:References:In-Reply-To; b=BEqSsteQhZjsiDwQJvffftyeAChuQgxAaQSsnpQeDa3Blvgzf2PdGhwgqA/NU2dx9 zyKrbuXwjhNRX/iSYWadhJXnHf5/3oj+hZNrhVqxsNN5BeSjfzE4/fwiqHSLOQVBPB EZ77tEgQfvXEWIUnG5BlFm3UDQJFrHJ3394sAd7E/x/d0Vunt2F22mpD83/eQtIrYf 5ocp4EbaTIA8GI41909kdil47wiJ6A7PFgfu0DFt8GyRezAhF23pBa1eJdD7+E3CTK 4cCK+szY94TfbY96EhyUcwF15D5pWJPlLUaPnPFfNGTbfXyE8gY8zDCtDyFrwgpDnw Nv0XvKbWZ7HdQ==
Message-ID: <20170904075644.Horde.924lndsmUEMRj_z7lcDTbgy@andreasschulze.de>
From: "A. Schulze" <sca@andreasschulze.de>
To: dnsop@ietf.org
References: <20170820014850.1072.qmail@ary.lan> <54f2e262-ed8c-67dd-21b0-83f50992e619@nic.cz>
In-Reply-To: <54f2e262-ed8c-67dd-21b0-83f50992e619@nic.cz>
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vvIlURaEzMwF2vgfrCFosZakFJI>
Subject: Re: [DNSOP] fragile dnssec, was Fwd: New Version
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 05:56:52 -0000

Petr Špaček:

> http://iepg.org/2017-07-16-ietf99/Fully%20automatic%20DNSSEC%20-%20final.pdf
>
> Feel free to play with it, we very much welcome feedback!
> Please direct further questions to Jaromír Talíř <jaromir.talir@nic.cz>.

update:

I followed the instructions. One day after publishing a CDNSKEY I  
received one email.
A week later my system detected .cz publish a DS record.

thanks .cz!
Andreas



From nobody Sun Sep  3 23:12:49 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1141243F6 for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 23:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 BEvCXXvGwbEH for <dnsop@ietfa.amsl.com>; Sun,  3 Sep 2017 23:12:44 -0700 (PDT)
Received: from mx23lb.world4you.com (mx23lb.world4you.com [81.19.149.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F4291201F8 for <dnsop@ietf.org>; Sun,  3 Sep 2017 23:12:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=/cJTyfP4yZy4BgW6HfmKYOqdzxgootqH3E4ZeIiYG9Q=;  b=S+0ubNorEtZmPzCEPWERhKDNKJLZ4JrkMoiNCOvudmMMj8UPHRB8Vw3aTpl9RfAOVMEBnMB0/HcLv96ewPphwHIiJgSIQHRH+qBNqYyCf+v47pj4JZDeSl20DJ7hNAgFS3KamEFGufYHRP5M6nyi2KQl+RxBc2a2jHtaqUYbqXY=;
Received: from [90.146.55.206] (helo=home.mail) by mx23lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dokci-0000HX-Kp; Mon, 04 Sep 2017 08:12:40 +0200
Message-ID: <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
In-Reply-To: <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org>
Date: Mon, 4 Sep 2017 08:12:39 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx23lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gItCdFwpQJ2FrpIFCZ-iwMV0BME>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 06:12:47 -0000

On Sun, September 3, 2017 23:38, Mark Andrews wrote:
>> ]On 4 Sep 2017, at 4:47 am, Walter H. <Walter.H@mathemainzel.info>
>> wrote:
>>
>> even if I fully ACK this, but 15 years ago, nobody said, that  ".local",
>> ... would conflict one day ...
>> and also the company I work for has decided at these times to use a
>> ".local" as internal domain and AD;
>> now it is impossible to change this ...
>
> Why would anyone tell you that “.local” would conflict when you were
> supposed
> to register a name *before* using it.

NAK: because there are two points:
the 1st: uniqueness is not a requirement here
the 2nd: global knowledge of locally used names might raise a security
problem ...

> If you are doing AD correctly you should be able to register you machines
> wherever
> they connect to the Internet and that requires a public registration.

you could that also say the other way round: if the folks had done their
job correct and made a DNS-pendant to RFC1918, many enterprises wouldn't
have the problems now, which are unresolveable ...

by the way: why are you discussing about DNSSEC for names that are used
only locally?


From nobody Mon Sep  4 01:26:22 2017
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D05B1321AA for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 PrCXg2_I6-5y for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:26:19 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6051126D0C for <dnsop@ietf.org>; Mon,  4 Sep 2017 01:26:18 -0700 (PDT)
Received: from [156.106.225.18] (unknown [156.106.225.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id A3DC12421529; Mon,  4 Sep 2017 08:26:15 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Jim Reid <jim@rfc1035.com>
X-Priority: 3 (Normal)
In-Reply-To: <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
Date: Mon, 4 Sep 2017 09:26:14 +0100
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
To: "Walter H." <Walter.H@mathemainzel.info>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/B4K_y9vLQK0_ER5BIks7wZTfFv0>
Subject: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 08:26:20 -0000

> On 4 Sep 2017, at 07:12, Walter H. <Walter.H@mathemainzel.info> wrote:
>=20
> by the way: why are you discussing about DNSSEC for names that are =
used
> only locally?

Why do you seem to assume there are never, ever any DNS security issues =
on the local net?
Why would someone want to deliberately configure things to prevent =
DNSSEC-aware applications and resolvers from working on the local net?


From nobody Mon Sep  4 01:54:52 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 393D113248B for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 zdv8pOSP1fjN for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:54:49 -0700 (PDT)
Received: from mx06lb.world4you.com (mx06lb.world4you.com [81.19.149.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E748A1321AA for <dnsop@ietf.org>; Mon,  4 Sep 2017 01:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=OBlUHnoAJheV/MT/3uNs9Zgj+zow4FGr6GmXXiknop8=;  b=SpTpT7r4HnoWkR+K5zIyQJHwybhxa4K6VDYus1qVKPSKcw6vT+Kdb+DVgNM2tObq7PzQBCBr5fHRP+boRJRo76wM+ZG2P71hqWuPUz+HqX0TJT02nJejT6ZWfPteNAr90gg4EBJgwGGCAJSrOucBLJWi/di8eSVLMWANIIXigIQ=;
Received: from [90.146.55.206] (helo=home.mail) by mx06lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1don9a-0006ak-0Y; Mon, 04 Sep 2017 10:54:46 +0200
Message-ID: <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>
In-Reply-To: <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com>
Date: Mon, 4 Sep 2017 10:54:44 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Jim Reid" <jim@rfc1035.com>
Cc: "Walter H." <walter.h@mathemainzel.info>, "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx06lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ih7Xrh7GiHoQPJ9zrOBqCRHvN0I>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 08:54:51 -0000

On Mon, September 4, 2017 10:26, Jim Reid wrote:
>
>> On 4 Sep 2017, at 07:12, Walter H. <Walter.H@mathemainzel.info> wrote:
>>
>> by the way: why are you discussing about DNSSEC for names that are used
>> only locally?
>
> Why do you seem to assume there are never, ever any DNS security issues on
> the local net?

when there are troubles on the local net, DNS security issues are the less
problem ...

I'd say: "either you trust the local net or not";

> Why would someone want to deliberately configure things to prevent
> DNSSEC-aware applications and resolvers from working on the local net?

because of its strange signature procedure: a zone doesn't have to be
resigned, when it changes ...


From nobody Mon Sep  4 01:58:53 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04E11321AA for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 aaKEDX57H-D3 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 01:58:50 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C417C13248B for <dnsop@ietf.org>; Mon,  4 Sep 2017 01:58:49 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 76E6624AE34; Mon,  4 Sep 2017 08:58:38 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 21E0316007F; Mon,  4 Sep 2017 08:58:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0A21016007E; Mon,  4 Sep 2017 08:58:45 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id MQhQcMZwtwNd; Mon,  4 Sep 2017 08:58:44 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A337E16005C; Mon,  4 Sep 2017 08:58:44 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 890C28411BA8; Mon,  4 Sep 2017 18:58:40 +1000 (AEST)
To: "Walter H." <walter.h@mathemainzel.info>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
In-reply-to: Your message of "Mon, 04 Sep 2017 08:12:39 +0200." <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
Date: Mon, 04 Sep 2017 18:58:40 +1000
Message-Id: <20170904085840.890C28411BA8@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/z0YQ4L_a8EPA9qR9NUeXKrOcJGo>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 08:58:52 -0000

In message <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>, "Walter
 H." writes:
> On Sun, September 3, 2017 23:38, Mark Andrews wrote:
> >> ]On 4 Sep 2017, at 4:47 am, Walter H. <Walter.H@mathemainzel.info>
> >> wrote:
> >>
> >> even if I fully ACK this, but 15 years ago, nobody said, that  ".local",
> >> ... would conflict one day ...
> >> and also the company I work for has decided at these times to use a
> >> ".local" as internal domain and AD;
> >> now it is impossible to change this ...
> >
> > Why would anyone tell you that “.local” would conflict when you were
> > supposed
> > to register a name *before* using it.
> 
> NAK: because there are two points:
> the 1st: uniqueness is not a requirement here
> the 2nd: global knowledge of locally used names might raise a security
> problem ...

Except you misses the entire point of getting a registered name,
that is to be able to use it safely without anyone trampling on its
use.  'home.arpa' is in the process of being registered so that it
can be used safely in the environment it is designed to be used in.

Yes, 'home.arpa' will be registered.  It's a different type of
registration to the one that is normally done by talking to your
friendly DNS registrar but it is a registration.

> > If you are doing AD correctly you should be able to register you machines
> > wherever
> > they connect to the Internet and that requires a public registration.
> 
> you could that also say the other way round: if the folks had done their
> job correct and made a DNS-pendant to RFC1918, many enterprises wouldn't
> have the problems now, which are unresolveable ...

Names are not addresses.  They have different properties.
 
> by the way: why are you discussing about DNSSEC for names that are used
> only locally?

I'm discussing about putting names through the DNSSEC validator and
not having the fail validation.  It is also possible to use DNSSEC
within home.arpa.  It requires more care especially if you have a
mobile device but it is possible.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 02:05:05 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8243A1321AA for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 u9ltKDLJtOha for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:05:02 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBF15126DFE for <dnsop@ietf.org>; Mon,  4 Sep 2017 02:05:02 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 055FD24AE34; Mon,  4 Sep 2017 09:04:51 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9AB3216005C; Mon,  4 Sep 2017 09:04:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 871D116007E; Mon,  4 Sep 2017 09:04:57 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id qn9TVw6XFVAR; Mon,  4 Sep 2017 09:04:57 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 31CCD16005C; Mon,  4 Sep 2017 09:04:57 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 4249F8411CFC; Mon,  4 Sep 2017 19:04:55 +1000 (AEST)
To: "Walter H." <walter.h@mathemainzel.info>
Cc: "Jim Reid" <jim@rfc1035.com>, dnsop WG <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>
In-reply-to: Your message of "Mon, 04 Sep 2017 10:54:44 +0200." <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>
Date: Mon, 04 Sep 2017 19:04:55 +1000
Message-Id: <20170904090455.4249F8411CFC@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/X4AWtDKZ0xn15qT80Itg-edGlAg>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 09:05:04 -0000

In message <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>, "Walter
 H." writes:
> On Mon, September 4, 2017 10:26, Jim Reid wrote:
> >
> >> On 4 Sep 2017, at 07:12, Walter H. <Walter.H@mathemainzel.info> wrote:
> >>
> >> by the way: why are you discussing about DNSSEC for names that are used
> >> only locally?
> >
> > Why do you seem to assume there are never, ever any DNS security issues on
> > the local net?
> 
> when there are troubles on the local net, DNS security issues are the less
> problem ...
> 
> I'd say: "either you trust the local net or not";
> 
> > Why would someone want to deliberately configure things to prevent
> > DNSSEC-aware applications and resolvers from working on the local net?
> 
> because of its strange signature procedure: a zone doesn't have to be
> resigned, when it changes ...

And no one said you have to use DNSSEC to sign any zone.  The
discussion is around making DNSSEC validating software work without
having to update all of it to support people using home.arpa.  That's
starts by having a delegation for home.arpa.

Mark

> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 02:10:07 2017
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 056B71321AA for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 1D93-IbWV8HU for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:10:03 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D2D126DFE for <dnsop@ietf.org>; Mon,  4 Sep 2017 02:10:03 -0700 (PDT)
Received: from [156.106.225.18] (unknown [156.106.225.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 4A55E2421529; Mon,  4 Sep 2017 09:10:01 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20170904090455.4249F8411CFC@rock.dv.isc.org>
Date: Mon, 4 Sep 2017 10:10:00 +0100
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFA87BD3-86F9-4A1D-B719-EE36DAC5D35B@rfc1035.com>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org>
To: "Walter H." <walter.h@mathemainzel.info>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bNuK1gprjcs66sr5lP27Tz70vOY>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 09:10:04 -0000

> I'd say: "either you trust the local net or not"

I'd say trust but verify. Everywhere. =3D> In this context always doing =
DNSSEC validation.


From nobody Mon Sep  4 02:50:10 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53E7B126B6E for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 o7g5oEoNY361 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 02:50:06 -0700 (PDT)
Received: from mx25lb.world4you.com (mx25lb.world4you.com [81.19.149.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EE821241FC for <dnsop@ietf.org>; Mon,  4 Sep 2017 02:50:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=Nk26VtnI0RPsIDxMyj3ruvZRz4BIUon2KFSFQnpFpKE=;  b=rCJnPe6v4KeanvODu+PjysaLS+EdmWNoN3Yr6GczQ3LLmd/z4P/iyjOCrw8lY3e8gY2Uf/5kgTxSY/Q5Lwpvd+DLYJqaIRsRCtWDhkHJ2oh7WEs+BFJeZdUP+Gq38MeFgvpBUC8nI5bParAlqAwtmW2fpVlbFIITBe443amu3dU=;
Received: from [90.146.55.206] (helo=home.mail) by mx25lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1doo16-0007x3-5C; Mon, 04 Sep 2017 11:50:04 +0200
Message-ID: <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>
In-Reply-To: <20170904090455.4249F8411CFC@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org>
Date: Mon, 4 Sep 2017 11:50:03 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: "Jim Reid" <jim@rfc1035.com>, "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx25lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rLgEMadicnWRXHlMv4ATL2l6xYM>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 09:50:08 -0000

> Except you misses the entire point of getting a registered name,
> that is to be able to use it safely without anyone trampling on its
> use.

where there anyone who said: "don't use it", 15 years ago?

> 'home.arpa' is in the process of being registered so that it
> can be used safely in the environment it is designed to be used in.

yes, but commonly for residental networks, not company/enterprise networks,
they want/need something shorter like ".corp", ".lan", ".local", ...

> Yes, 'home.arpa' will be registered.  It's a different type of
> registration to the one that is normally done by talking to your
> friendly DNS registrar but it is a registration.

exact such a name but a TLD is needed for companies/enterprises in order
to prevent new ones doing the mistakes of old ones ..., and having the
safety not having a conflict in the future ...

> Names are not addresses.  They have different properties.

that is not the point,
the point is, that in those days where these companies decided to use
.local, .corp, ... such a paper prevented these decisions and now it could
have been expanded with DNSSEC features ...

just guess what would have happened when there was no RFC1918; by the way,
I would not have any problem changing my internal IPv4 addresses from e.g.
10.x.x.x to let's say 52.x.x.x - it is only a thought;

companies that use .local as their internal domain name and/or Active
Directory have no problem as long as there is no system that insists on
using mDNS for .local as specified in RFC6762


From nobody Mon Sep  4 03:42:03 2017
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE1D126DD9 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 03:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 P9js_DXsgLB5 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 03:41:59 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [192.36.115.55]) by ietfa.amsl.com (Postfix) with ESMTP id 6654A1241FC for <dnsop@ietf.org>; Mon,  4 Sep 2017 03:41:59 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 102E89D61; Mon,  4 Sep 2017 12:41:57 +0200 (CEST)
Date: Mon, 4 Sep 2017 12:41:57 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: "Walter H." <Walter.H@mathemainzel.info>
Cc: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20170904104157.GD18082@besserwisser.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0/kgSOzhNoDC5T3a"
Content-Disposition: inline
In-Reply-To: <59AC4E42.9080600@mathemainzel.info>
X-URL: http://vvv.besserwisser.org
X-Clacks-Overhead: "GNU Sir Terry Pratchett"
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/i_wiRbSIZIF593VtYdTGMsw4HaM>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 10:42:02 -0000

--0/kgSOzhNoDC5T3a
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: [DNSOP] DNS names for local networks - not only home residenta=
l networks ... Date: Sun, Sep 03, 2017 at 08:47:30PM +0200 Quoting Walter H=
=2E (Walter.H@mathemainzel.info):
> On 03.09.2017 06:32, M=C3=A5ns Nilsson wrote:
> > Corporate environments are a somewhat different matter, since you can
> > expect them to own their own domain name and have people who can set up
> > devices to use it.
> > > BUT this need not necessarily be a public domain ..., just think of A=
ctive
> > > Directory Domains ...
> > AD is DNS, and it follows the same rules.
> yes and no; AD is more, and so many companies got the advice to use a dom=
ain
> name,
> that is NOT public, because it is not internet ...

A lot of Microsoft -focused consultants have, say, a very confused view
of what the Internet is, and especially what DNS is. Consequently,
a lot of FUD is propagated about the AD implementation.  Reading the
TechNet whitepapers and combining that data with some testing  soon
reveals that the only strange thing in AD DNS is the use of GSSAPI to
secure updates. This has seen 3rd party implementation, and is used in
both commercial and open-source software to provide DNS to AD. It is
only DNS, well thought out and used do a lot of things.

> >   A sub-domain, a separate domain
> > or two-face (using the same domain name as you public-facing resources
> > but a different set of authoritative servers and some careful setup of
> > full-service resolvers), all work. The single thing that does not work
> > is to use name-space you do not own (like LOCAL or a domain name from a
> > non-existent TLD, like "web". Ooops. It does now...) and hope it doesn't
> > escape. Or that somebody registers the name and tries to impersonate yo=
u.

> even if I fully ACK this, but 15 years ago, nobody said, that  ".local", =
=2E..
> would conflict one day ...

Nobody said that it would be conflict-free forever either. The best
available strategy was, and is, to use names within a domain you have
some control over.

> and also the company I work for has decided at these times to use a ".loc=
al"
> as internal domain and AD;
> now it is impossible to change this ...

Bad advice does not improve with aging.=20
=20
> I for myself use a ".home.arpa" as internal name (I'm no company just a
> citizen),
> and for IPv6 connections I use a subdomain of my public domain,
> which is only used to get resolved correctly ...
> e.g.  the IPv6 of my proxy resolves to  proxy.sub.example.com and
> proxy.sub.example.com resolved to this IPv6 ...
> and router (firewall) blocks the whole prefix to be connected from outside
> (internet) ...

Practical operational experience suggests that firewalls leak. Not in the e=
xpected
ways, but in new unforseen trickles.=20

The best available strategy was, and is, to use names within a domain
you have some control over. It seems I'm repeating myself. My
apologies. I'll quit now.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE           SA0XLR            +46 705 989668
The PILLSBURY DOUGHBOY is CRYING for an END to BURT REYNOLDS movies!!

--0/kgSOzhNoDC5T3a
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJZrS31AAoJEA4LceDT9hu0xtkP/33mqBfzoOeQbp2ZsCbjF/aq
RBJPbgEizjKunOaeyUOkfnXR7nSDMY8oYeSBULpGrV97x0SUN/fZPQQrUyaxxVCb
DYEOwCaGOZofGbnt4tTC5PAttH6sH6N7Amu7B8yld07ygdq9Yl+npML5SzISOSH7
FvK3s+ePdTQENnXX7wE9rbfQrOOGMExXG2F0/hOwJPdhoEwLuMlmmJgRAOPBG4vH
TPQdkhXOirbTn7KDxFS0MRXSWH/DU90BUxnUvgmkm1UNhPRmJM5yEOIlIO11Wqy7
o7NnkLZM8dtMgc3mmvnsHoAY8dYIjuSJctlaUxf10SKe1VXJExA1+84yAHvfEzv5
DoQZTJU/PrtcGcvXTlP8MVoruuYuI/N2Jf2Qa4MpsbTChuHTT+npeFKUwqBiL8q8
zKr92XpQa/WDPREW51Az4gUPHspd05//CeUEex/z9IOET3SehK6LhnoQ46bKWRT8
qIX5AR4SuH+D33MWl+d+vQCkQTFn4IdWDalyogs5mtMbXAkKNCFxcOjG5S/BsTWS
Ut95na/F4qrzk+XRfUsnkKHSCa++ZJvJOHUeArvE95CeNcoz4wB0rgxu+3PlOVUZ
bCt4kyr7bGzJU8IsbC0oZMC4eB2HoIB3MHk2aGMr6gAX55VqeCdzfkzKW8mBdXJg
vjNt/46Rvx8J+6VKF3o6
=GjDu
-----END PGP SIGNATURE-----

--0/kgSOzhNoDC5T3a--


From nobody Mon Sep  4 05:22:33 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F3612ECEC for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 9PNE8XPiLkyI for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:22:30 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9373A126DD9 for <dnsop@ietf.org>; Mon,  4 Sep 2017 05:22:30 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id F1CA524AE34; Mon,  4 Sep 2017 12:22:18 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id AA3A016005C; Mon,  4 Sep 2017 12:22:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 95DFA16007F; Mon,  4 Sep 2017 12:22:25 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0Bhg-AkgZ14U; Mon,  4 Sep 2017 12:22:25 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 451A516005C; Mon,  4 Sep 2017 12:22:25 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C270F8413534; Mon,  4 Sep 2017 22:22:22 +1000 (AEST)
To: "Walter H." <walter.h@mathemainzel.info>
Cc: "Jim Reid" <jim@rfc1035.com>, "dnsop WG" <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>
In-reply-to: Your message of "Mon, 04 Sep 2017 11:50:03 +0200." <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>
Date: Mon, 04 Sep 2017 22:22:22 +1000
Message-Id: <20170904122222.C270F8413534@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1fqcAtFoEo4nPT66FAYtz_rux7s>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 12:22:32 -0000

In message <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>, "Walter H." writes:
> > Except you misses the entire point of getting a registered name,
> > that is to be able to use it safely without anyone trampling on its
> > use.
> 
> where there anyone who said: "don't use it", 15 years ago?

Yes.  There were lots that discourage the use of .local, lan,
.corp etc.  Just becaue you didn't hear from them doesn't mean
they weren't out there.

> > 'home.arpa' is in the process of being registered so that it
> > can be used safely in the environment it is designed to be used in.
> 
> yes, but commonly for residental networks, not company/enterprise networks,
> they want/need something shorter like ".corp", ".lan", ".local", ...

Want maybe, need absolutely not.
 
> > Yes, 'home.arpa' will be registered.  It's a different type of
> > registration to the one that is normally done by talking to your
> > friendly DNS registrar but it is a registration.
> 
> exact such a name but a TLD is needed for companies/enterprises in order
> to prevent new ones doing the mistakes of old ones ..., and having the
> safety not having a conflict in the future ...
> 
> > Names are not addresses.  They have different properties.
> 
> that is not the point,
> the point is, that in those days where these companies decided to use
> .local, .corp, ... such a paper prevented these decisions and now it could
> have been expanded with DNSSEC features ...

Everyone was told to register the domain you want to use, there was
no exception for active directory.

> just guess what would have happened when there was no RFC1918; by the way,
> I would not have any problem changing my internal IPv4 addresses from e.g.
> 10.x.x.x to let's say 52.x.x.x - it is only a thought;

IPv6 would have been deployed a lot sooner. :-)
 
> companies that use .local as their internal domain name and/or Active
> Directory have no problem as long as there is no system that insists on
> using mDNS for .local as specified in RFC6762

Except such systems exist.  Go look at what a Mac does.  ping for
test.local and look and port 5353 traffic and compare it to port 53
traffic.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 05:54:48 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93EBE13202D for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 uxVu4Jpe9I0V for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:54:44 -0700 (PDT)
Received: from mx01lb.world4you.com (mx01lb.world4you.com [81.19.149.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEA9126BFD for <dnsop@ietf.org>; Mon,  4 Sep 2017 05:54:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=KsX1IidVlQ1iKetas43R9CHX5Cflzg7Wf1WieXylnBM=;  b=weDdxm5AgFhWuE/9et/XxRaQkxzOIMM68UiI+TpcHac+9qiUOWMLIzRuJ9sscXDkQhe9q66hjSILPrvunhQTjjp367pRbHT6zIZH0T1ipIter2vH7Z5UhvqDY+UluqeIJlAzSekIXQhBavq0th0IATQo/1rGa6FByncXOVgv0AI=;
Received: from [90.146.55.206] (helo=home.mail) by mx01lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1doqtk-0002s0-LO; Mon, 04 Sep 2017 14:54:40 +0200
Message-ID: <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>
In-Reply-To: <20170904122222.C270F8413534@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org>
Date: Mon, 4 Sep 2017 14:54:39 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: "Walter H." <walter.h@mathemainzel.info>, "Jim Reid" <jim@rfc1035.com>, "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx01lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rTQu74A-L9UdHjrgwKaPd3BRWzw>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 12:54:46 -0000

On Mon, September 4, 2017 14:22, Mark Andrews wrote:
>
> In message <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>,
> "Walter H." writes:
>> where there anyone who said: "don't use it", 15 years ago?
>
> Yes.  There were lots that discourage the use of .local, lan,
> .corp etc.  Just becaue you didn't hear from them doesn't mean
> they weren't out there.

a discourage is not a "don't use" :-)

>> > 'home.arpa' is in the process of being registered so that it
>> > can be used safely in the environment it is designed to be used in.
>>
>> yes, but commonly for residental networks, not company/enterprise
>> networks,
>> they want/need something shorter like ".corp", ".lan", ".local", ...
>
> Want maybe, need absolutely not.
question: why isn't this the answer of a car dealer?

> Everyone was told to register the domain you want to use, there was
> no exception for active directory.

not really, at those days only a few TLDs where possible, the many TLDs
came some years later ...

by the way: where is the problem with .home or .corp?
I ask this, because at my hoster I pre-reserved my "local domain" - a
.home, that I have used for many years several zears ago and nothing
happened ...

> IPv6 would have been deployed a lot sooner. :-)

not really, my ISP is still IPv4 only ..., my IPv6 connectivity is a
HE-tunnel ...
and the brand new OS from Microsoft still has the bugs inside: TEREDO, ...
which I had to deactivate first, before it is usable with IPv6 at all ...

> Except such systems exist.  Go look at what a Mac does.  ping for
> test.local and look and port 5353 traffic and compare it to port 53
> traffic.

I know, this RFC was written by Apple;

no Apple no problem, I would say :-)



From nobody Mon Sep  4 05:57:04 2017
Return-Path: <petr.spacek@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65FB1132960 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 NZkdsXqQwkaB for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 05:57:00 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8092713217D for <dnsop@ietf.org>; Mon,  4 Sep 2017 05:57:00 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:dc5d:d8ff:fe1c:f6e3] (unknown [IPv6:2001:1488:fffe:6:dc5d:d8ff:fe1c:f6e3]) by mail.nic.cz (Postfix) with ESMTPSA id DA0CD617DF for <dnsop@ietf.org>; Mon,  4 Sep 2017 14:56:58 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1504529818; bh=QsmE3nkXS4tX1jbf4g0D222vRC+wi3Fvy3NfTEQg4w0=; h=To:From:Date; b=wJDQpa4pKWelU/7JGL9OUZIUYkoUF3kT3Qxotdzkz+DitxFbrdsvDaGHDn1gP75XM Q7LcsiGhDanjJlT1f9tf5+plywWqUDXuGWPOsrEQbDFAJsaSefIUMexyX9arGyZxEN mDM/z2WCRwqPXx5noT6eU9EsINHZ35wuxNv1vNuI=
To: dnsop@ietf.org
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <3ab6b4f3-e963-79e4-5f55-c87d450b23fd@nic.cz>
Date: Mon, 4 Sep 2017 14:56:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/75TDtyrWPDtLpgTEwqo3VIbaT2g>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 12:57:03 -0000

On 4.9.2017 11:50, Walter H. wrote:
>> Except you misses the entire point of getting a registered name,
>> that is to be able to use it safely without anyone trampling on its
>> use.
> 
> where there anyone who said: "don't use it", 15 years ago?
> 
>> 'home.arpa' is in the process of being registered so that it
>> can be used safely in the environment it is designed to be used in.
> 
> yes, but commonly for residental networks, not company/enterprise networks,
> they want/need something shorter like ".corp", ".lan", ".local", ...

I would like to comment on
'vendor told us and we followed his instructions'.
Maybe it is time to follow the new docs, e.g.:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices

Software and its docs have bugs which get fixed over time and there is
not way around it. Configuration has to follow the suit.


Please keep in mind that reserving a new name will not magically solve
the issue.

1. Existing systems will stay broken *unless* the reservation is for the
same string as used by particular network. Certainly this will not be
the case for all the broken installations.

In other words, some networks will stay non-complaint whatever dnsop
will do, which means that the broken networks will either get fixed over
time or stay broken. I do not see dnsop having real influence over this
aspect of network operation, sorry.


2. Also, reserving a random string does not solve problem of VPNs
between companies (customer using VPN to supplier's network, for
example), company mergers, etc.

If we reserved string 'example.', how it helped to solve the problem
when your company X needs to establish VPN tunnel to company Y internal
network to access its systems? How does it help if company X merges with
company Y?

Really, unique strings are the way to go.

Petr Špaček  @  CZ.NIC


> 
>> Yes, 'home.arpa' will be registered.  It's a different type of
>> registration to the one that is normally done by talking to your
>> friendly DNS registrar but it is a registration.
> 
> exact such a name but a TLD is needed for companies/enterprises in order
> to prevent new ones doing the mistakes of old ones ..., and having the
> safety not having a conflict in the future ...
> 
>> Names are not addresses.  They have different properties.
> 
> that is not the point,
> the point is, that in those days where these companies decided to use
> .local, .corp, ... such a paper prevented these decisions and now it could
> have been expanded with DNSSEC features ...
> 
> just guess what would have happened when there was no RFC1918; by the way,
> I would not have any problem changing my internal IPv4 addresses from e.g.
> 10.x.x.x to let's say 52.x.x.x - it is only a thought;
> 
> companies that use .local as their internal domain name and/or Active
> Directory have no problem as long as there is no system that insists on
> using mDNS for .local as specified in RFC6762


From nobody Mon Sep  4 07:54:20 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D980C13219F for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 07:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 dXfGIAYTTvom for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 07:54:17 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A24C912426E for <dnsop@ietf.org>; Mon,  4 Sep 2017 07:54:17 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 360ED28058E; Mon,  4 Sep 2017 16:54:16 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 3014A2805B2; Mon,  4 Sep 2017 16:54:16 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 296AF28058E; Mon,  4 Sep 2017 16:54:16 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 263CD606D941; Mon,  4 Sep 2017 16:54:16 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 13F5B40360; Mon,  4 Sep 2017 16:54:16 +0200 (CEST)
Date: Mon, 4 Sep 2017 16:54:16 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Walter H." <Walter.H@mathemainzel.info>
Cc: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20170904145416.migl2p4h4ctzokqd@nic.fr>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59A9BCA2.6060008@mathemainzel.info>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.001846, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.4.144216
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Vbir4IdvIZxXtbFnFigtIB0Z1_E>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 14:54:19 -0000

On Fri, Sep 01, 2017 at 10:01:38PM +0200,
 Walter H. <Walter.H@mathemainzel.info> wrote 
 a message of 125 lines which said:

> not one registry is willing to give me a domain - even when I pay
> for this - which I only use in a LAN, and the authoritativ DNS
> servers would then just be 127.0.0.1 or ::1

That's clearly not true. .fr, for instance (but it is not the only
one) allows registration of a domain without name servers (or with
funny name servers such as ::1).



From nobody Mon Sep  4 07:59:22 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5511321AF for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 07:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 QeojQWx4nRWb for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 07:59:17 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7901321A1 for <dnsop@ietf.org>; Mon,  4 Sep 2017 07:59:17 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 497E028058E; Mon,  4 Sep 2017 16:59:16 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 434FD2805B2; Mon,  4 Sep 2017 16:59:16 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 3C72F28058E; Mon,  4 Sep 2017 16:59:16 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 39410606D941; Mon,  4 Sep 2017 16:59:16 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 318E640360; Mon,  4 Sep 2017 16:59:16 +0200 (CEST)
Date: Mon, 4 Sep 2017 16:59:16 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Walter H." <walter.h@mathemainzel.info>
Cc: Mark Andrews <marka@isc.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Message-ID: <20170904145916.ccuvetldvao7s47h@nic.fr>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.031949, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.4.144816
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5RklFA5Joq_gy7EDk9C4lE-AsLc>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 14:59:20 -0000

On Mon, Sep 04, 2017 at 08:12:39AM +0200,
 Walter H. <walter.h@mathemainzel.info> wrote 
 a message of 23 lines which said:

> the 1st: uniqueness is not a requirement here

Serious mistake. Companies merge, and are bought. Any netadmin had, at
least once in his professional life, to manage RFC 1918 networks
merging and collisioning after some corporate change.

If it's not realistic to switch from .local to the proper
.private.mycompany.com to follow Best Practices, then it is certainly
not realistic to do so when two companies merge, and their .local
collide.

> the 2nd: global knowledge of locally used names might raise a
> security problem ...

You don't have to make the nameservers reachable from the outside. Most
of the time, name servers for .private.mycompany.com are
internal-only.


From nobody Mon Sep  4 08:02:04 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A7312426E for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 JXhaa0Y1phdm for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:02:00 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C07132CE7 for <dnsop@ietf.org>; Mon,  4 Sep 2017 08:01:53 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 054FC28058E; Mon,  4 Sep 2017 17:01:52 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id F39DD2805B2; Mon,  4 Sep 2017 17:01:51 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id ECCCF28058E; Mon,  4 Sep 2017 17:01:51 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id E9A75606D941; Mon,  4 Sep 2017 17:01:51 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id E1EA040360; Mon,  4 Sep 2017 17:01:51 +0200 (CEST)
Date: Mon, 4 Sep 2017 17:01:51 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Walter H." <walter.h@mathemainzel.info>
Cc: Jim Reid <jim@rfc1035.com>, dnsop WG <dnsop@ietf.org>
Message-ID: <20170904150151.h7v3da7s3jp4yhec@nic.fr>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000202, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.4.145116
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yEccOqbYNCVFzcRh5QxXPY5orPU>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 15:02:03 -0000

On Mon, Sep 04, 2017 at 10:54:44AM +0200,
 Walter H. <walter.h@mathemainzel.info> wrote 
 a message of 25 lines which said:

> I'd say: "either you trust the local net or not";

I don't claim to be a security expert, but I think it is a
mistake. Many local networks are vulnerable to packets with an
internal address coming from the outside, routing attacks diverting
traffic outside, etc. Not to mention the internal attacks, for
instance by a MS-Windows zombie.

It seems to me that having TLS, DNSSEC and SSH and so on even in the
local net is Best Practice.


From nobody Mon Sep  4 08:22:04 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7604F129C41 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 md7TRmKhDZSs for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:21:59 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3B1313219F for <dnsop@ietf.org>; Mon,  4 Sep 2017 08:21:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=ILwDvGoOnHPnA6ZZ0mVP6zaLVja/JIUn76OCS5xamwg=;  b=hwpTVHspOgl2KLXgfZ/Ce41hkeDNhht7/tEX2cDBmktw0q32Ei9ey0FsSF0kWPZVOn5LLMr3Tur+EZziDTi9Rtzal23Qczn7NIycx8L5DlcQPNDP9QaZGi860s0Sw7IhIYe5+YfeOjmXVb1UUMEBpih9Xsr/0ypZDMDcx1wzAus=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1dotCF-0000X2-PB; Mon, 04 Sep 2017 17:21:55 +0200
Message-ID: <59AD6F92.9070108@mathemainzel.info>
Date: Mon, 04 Sep 2017 17:21:54 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: dnsop WG <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904150151.h7v3da7s3jp4yhec@nic.fr>
In-Reply-To: <20170904150151.h7v3da7s3jp4yhec@nic.fr>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070509090904080708040901"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2BKkPBPegWR6WAevf30_tNuqoOk>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 15:22:02 -0000

This is a cryptographically signed message in MIME format.

--------------ms070509090904080708040901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 04.09.2017 17:01, Stephane Bortzmeyer wrote:
> On Mon, Sep 04, 2017 at 10:54:44AM +0200,
>   Walter H.<walter.h@mathemainzel.info>  wrote
>   a message of 25 lines which said:
>
>> I'd say: "either you trust the local net or not";
> ..., but I think it is a
> mistake.
not really, when  there is a security problem, DNS is the less one ...
and I didn't say, that a locally running resolver would not be allowed=20
to validate DNSSEC;
but there needn't be a DNSSEC signed local only zone, as the signature=20
and zone content comes from the same host;
you can of course validate your own local only zone, nobody prevents you =

from doing so, but it is somewhat strange;
and the fact that a change of the zone doesn't need to be resigned=20
raises problems to;

  Many local networks are vulnerable to packets with an
internal address coming from the outside, routing attacks diverting
traffic outside, etc. Not to mention the internal attacks, for
instance by a MS-Windows zombie.

even this is true, DNSSEC for the local zones doesn't make it any better;=

as I said, when there is a security problem DNS is the less one ...

> It seems to me that having TLS, DNSSEC and SSH and so on even in the
> local net is Best Practice.
yes and no; when operating a local  mail server that uses TLS for IMAP,=20
SMTP, then
a Anti-virus has to break TLS in order to scan before it gets to the=20
client ...


--------------ms070509090904080708040901
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTA0MTUyMTU0
WjAjBgkqhkiG9w0BCQQxFgQUSqE7+39tU3G/uNqtpHpgNPuYks0wbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAI+CNa7QeXvYH4H1
dTsSnWFVF+SAcQP2RJamORcPzfJfinnL8zmux1DPukhR4Kvg6QhA4q1lSKV1NNlucLxE6Ejw
WggSFX9AAyOmVHbOINxXHR2ygvoyibj71pg+twmovX0JIjGDK4TmZs2JaxkWYYEkIEzKUm/M
JGodKJWp60xdcskJspaZqOJUPtFLzT66JH4KwaN4o8SRebs/b+nEcivkM67cPfF6J+ePNaiS
MJI1s1MQvOc8sdhSoFqXBtztzK8nPMbySnzjyq9rWaNqOaQipeaAMJ9p3K3XQedfEoLar81m
9JZHQBahXH3VVHDbGp+yHoSd3qlyxKIoFvamcnIAAAAAAAA=
--------------ms070509090904080708040901--


From nobody Mon Sep  4 08:25:23 2017
Return-Path: <Walter.H@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E569F132026 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 msgIgI4-Vnqq for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:25:20 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A7EB12426E for <dnsop@ietf.org>; Mon,  4 Sep 2017 08:25:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=9X8vpDZV110PSPoAI2BMNTGbBVcvvEGdhGdXKCN4Bl4=;  b=BnyXUgOGsyjfyL/8MzXnhBUvBnI15PGBd5rTbNUdOAkEUp7EStgrz1v5vccSmkuhPfaQ16YtWJB0rAtHyPv4K/lplowu1Z6xkozwpB90FIVn3a0NGIl4rm9vlbQsOslh+XNM9H0kN44GQBfi5xnIBE00iHtvt8SuqFqbDE2ppOw=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <Walter.H@mathemainzel.info>) id 1dotFW-00016z-UQ; Mon, 04 Sep 2017 17:25:19 +0200
Message-ID: <59AD705E.5010203@mathemainzel.info>
Date: Mon, 04 Sep 2017 17:25:18 +0200
From: "Walter H." <Walter.H@mathemainzel.info>
Organization: Home
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170904145416.migl2p4h4ctzokqd@nic.fr>
In-Reply-To: <20170904145416.migl2p4h4ctzokqd@nic.fr>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070002080302080009020101"
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: Walter.H@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4lYFU5Hiil7JV5SwWGTJguO3zbc>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 15:25:22 -0000

This is a cryptographically signed message in MIME format.

--------------ms070002080302080009020101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 04.09.2017 16:54, Stephane Bortzmeyer wrote:
>
> That's clearly not true. .fr, for instance (but it is not the only
> one) allows registration of a domain without name servers (or with
> funny name servers such as ::1).
>
this might be a mistake of mine, as I meant registrar, hoster which I=20
considered ...



--------------ms070002080302080009020101
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKBDCC
BOgwggPQoAMCAQICDkgbagkTvYAkyl0i8BTzMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsT
F0dsb2JhbFNpZ24gUm9vdCBDQSAtIFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQD
EwpHbG9iYWxTaWduMB4XDTE2MDYxNTAwMDAwMFoXDTI0MDYxNTAwMDAwMFowXTELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24g
UGVyc29uYWxTaWduIDIgQ0EgLSBTSEEyNTYgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBALaWaJNl/SwB7GKjDVS/i8ukQ5Gimq+xg/K1bW/Z8OrczxZ71xnjhAOF+cYf
cI8fbEnFaRkecJE4NX4CSF05axhEpmqlyHT0XfWEPmMfcUSCCD7tyaf26W4mQSmAyUm6/9l2
oKO7G/Z530so00p7nFHCD2VQoZ+oSp3lRgSNg0/cssg9z5ghCZhMwPGPeqk/NyZlR9hmj0km
wsNAvmY9bP86rSlG8BOc4fLrmaeLwtNfUG2iDm/HBpc4L06hjkcCtIMA2KTjukEHYOXdN1ry
B8E7p5yXaC6376lINrzpaaiZqkfpx/ZR0vmxLLbFSbWYnlNT2vty83wP+HE+1wP6Z8MCAwEA
AaOCAbUwggGxMA4GA1UdDwEB/wQEAwIBBjBqBgNVHSUEYzBhBggrBgEFBQcDAgYIKwYBBQUH
AwQGCCsGAQUFBwMJBgorBgEEAYI3FAICBgorBgEEAYI3CgMEBgkrBgEEAYI3FQYGCisGAQQB
gjcKAwwGCCsGAQUFBwMHBggrBgEFBQcDETASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQW
BBRpcoJiMWeVRIV3kYDEBDZJnXsLYTAfBgNVHSMEGDAWgBSP8Et/qC5FJK5NUPpjmove4t0b
vDA+BggrBgEFBQcBAQQyMDAwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwMi5nbG9iYWxzaWdu
LmNvbS9yb290cjMwNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5nbG9iYWxzaWduLmNv
bS9yb290LXIzLmNybDBnBgNVHSAEYDBeMAsGCSsGAQQBoDIBKDAMBgorBgEEAaAyASgKMEEG
CSsGAQQBoDIBXzA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAqJ3NMsx8Z+ILUNelXHCjZuIl7+q0tlMw
bocSN1wz4sIoVuOTvUWV81jYFXFM8+SCiRS+/qXMR73rBlSCPua/vvXqiPV5xCgiC4x69g4L
4yquSZoOm8In8my2G1VKAbYZ4WhQdFi8EkUYT67eXhsTMOdVJjSAov4UigSrB4RhUhGiUAC2
cuBy9BFnbhOiC2AI1+gUl0Q7RxXlD3XW+On+R3+a8yExi7J/QSKaDla4EvO/DuCZ31FkItvc
gX5++R2o4nxbzwvrqp/q3FZ766S4LCzmBv+uJFl/xUR/PpoVXvpnEl98bFKXMSvavby01ba6
FP8iVJhAuDnB+XULGxwaozCCBRQwggP8oAMCAQICDDf7Me/cd27Vi+FlDzANBgkqhkiG9w0B
AQsFADBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UE
AxMqR2xvYmFsU2lnbiBQZXJzb25hbFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczMB4XDTE3MDQy
NDEwNDQxOFoXDTIwMDQyNDEwNDQxOFowVTELMAkGA1UEBhMCQVQxGzAZBgNVBAMTEldhbHRl
ciBIb2VobGh1Ym1lcjEpMCcGCSqGSIb3DQEJARYad2FsdGVyLmhAbWF0aGVtYWluemVsLmlu
Zm8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDROn0wc2eBzHcRoKiSnUFz1H4T
SN5QEKhssd+B8F0YMDxEzXyvnOeCLAN+8+ui/fyZ0g1A8qgWIGkerNeJJgVes9Xf5EpemE5b
zksNPIoVQVB7sBfWezlJ6E12FUNssdLdcQlVqNtFnHtfZV0SD0BS87mW5GL75Ay8XpSkwwTV
6XpIAcKRyd7EFCw+7g2Udp/ZAjPZ4X7oZl8sFFlOClPvWu8LCjbnDcWHpE93QeXnmMx86LQg
tACrTy1PDX0yAOeCTan6F3sX0tz5Cp8sWduQiMaKof8yxW/t2V7BJwXhZhiDhax3y/AFREOH
NC5dJ2w1sFiwidK7sljogU7/orGHAgMBAAGjggHaMIIB1jAOBgNVHQ8BAf8EBAMCBaAwgZ4G
CCsGAQUFBwEBBIGRMIGOME0GCCsGAQUFBzAChkFodHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24u
Y29tL2NhY2VydC9nc3BlcnNvbmFsc2lnbjJzaGEyZzNvY3NwLmNydDA9BggrBgEFBQcwAYYx
aHR0cDovL29jc3AyLmdsb2JhbHNpZ24uY29tL2dzcGVyc29uYWxzaWduMnNoYTJnMzBMBgNV
HSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxz
aWduLmNvbS9yZXBvc2l0b3J5LzAJBgNVHRMEAjAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24yc2hhMmczLmNybDAlBgNVHREE
HjAcgRp3YWx0ZXIuaEBtYXRoZW1haW56ZWwuaW5mbzAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
KwYBBQUHAwQwHQYDVR0OBBYEFOQybe9sZCmROEwJqrOUU1qsTrgqMB8GA1UdIwQYMBaAFGly
gmIxZ5VEhXeRgMQENkmdewthMA0GCSqGSIb3DQEBCwUAA4IBAQBY5Zn+1HTT58xtZQgu1IcN
UI9t2PC0ps6sELyN3eCBvqYiqk5D8J58hNl9j0hnht5oM0aKVgTL1GNFu6J9DDd3Bk2sNmG6
8uIvo0NsJAFk23lMzKt+YOm3C6+oveuxICFhHeiTxn9z2jLfU+xYLg8UXpSl5U6m0uZcVoLA
YYYhLgpaSM8jNYgAv8U2NVK+f8hd4AVEpwyF2edKbZTAdj/iDmjmOm9lkUIzacemNR8DRxiD
Eb2XTZa5pcrsPOe1bisJ5wcHoIx+217fm8WJF7Vk2amB9fg8AM3cGU7V7D2Ynbg5tJdV5Et6
ff+sk9Fv1HRaFDqKQVorlDY1P5h1HsoxMYIDYTCCA10CAQEwbTBdMQswCQYDVQQGEwJCRTEZ
MBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xvYmFsU2lnbiBQZXJzb25h
bFNpZ24gMiBDQSAtIFNIQTI1NiAtIEczAgw3+zHv3Hdu1YvhZQ8wCQYFKw4DAhoFAKCCAckw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwOTA0MTUyNTE4
WjAjBgkqhkiG9w0BCQQxFgQUtDS0aLWhbbpgKh5nmNueLWHLjokwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB8BgkrBgEEAYI3EAQx
bzBtMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQD
EypHbG9iYWxTaWduIFBlcnNvbmFsU2lnbiAyIENBIC0gU0hBMjU2IC0gRzMCDDf7Me/cd27V
i+FlDzB+BgsqhkiG9w0BCRACCzFvoG0wXTELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2Jh
bFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2JhbFNpZ24gUGVyc29uYWxTaWduIDIgQ0EgLSBT
SEEyNTYgLSBHMwIMN/sx79x3btWL4WUPMA0GCSqGSIb3DQEBAQUABIIBAAt+clmIwwZe4b69
9LZ9b6+RdwVB+Ui1IWHfAM8LllEn4OotWl76zvNvIiX7XqKqjITvUWUzoqdp6rR/6GT344Ir
YStko5Fj8koz+9h6Xnoj2eHhBvA0cG+A2XHA349K6UyHmU92Nh40SZKWK8qAuQZIhqhX3zT/
0p221+GgklFi/N+kpVP3QjzTHNNzlPKisAJCv/BSs5KzfmGkiJWbpMwODdLlYZ8+7b5C+WSY
ofMPzic8CFuKJIWVmAU2it1NYt5Kavi5k4VjsCSF0wv2uyUNh6y3ZtXXG/ncwDYLTh2gVogp
wWCjzNNLV1EzOpNgiysp6KdvXlMdcxpl/nPy1hUAAAAAAAA=
--------------ms070002080302080009020101--


From nobody Mon Sep  4 08:28:33 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6F0132026 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 p1--Xe8g_xNY for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 08:28:30 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C04D613219F for <dnsop@ietf.org>; Mon,  4 Sep 2017 08:28:30 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 500F8280591; Mon,  4 Sep 2017 17:28:29 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 4A3762805B3; Mon,  4 Sep 2017 17:28:29 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 43884280591; Mon,  4 Sep 2017 17:28:29 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 3EAF860286A3; Mon,  4 Sep 2017 17:28:29 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 3232E40360; Mon,  4 Sep 2017 17:28:29 +0200 (CEST)
Date: Mon, 4 Sep 2017 17:28:29 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Walter H." <Walter.H@mathemainzel.info>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop WG <dnsop@ietf.org>
Message-ID: <20170904152829.tloxmujrwubliaqs@nic.fr>
References: <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904150151.h7v3da7s3jp4yhec@nic.fr> <59AD6F92.9070108@mathemainzel.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59AD6F92.9070108@mathemainzel.info>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000009, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.4.151816
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Bvd61hi4kZ2WB-34fpEh3-HqxEg>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 15:28:32 -0000

On Mon, Sep 04, 2017 at 05:21:54PM +0200,
 Walter H. <Walter.H@mathemainzel.info> wrote 
 a message of 114 lines which said:

> when operating a local mail server that uses TLS for IMAP, SMTP,
> then a Anti-virus has to break TLS in order to scan before it gets
> to the client

Which is also a very bad idea, giving the current state of such tools:

http://users.encs.concordia.ca/~mmannan/publications/ssl-interception-ndss2016.pdf

https://jhalderm.com/pub/papers/interception-ndss17.pdf


From nobody Mon Sep  4 11:43:01 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A289D126B6E for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 11:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 4DCto6-apOr9 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 11:42:58 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C74AF124239 for <dnsop@ietf.org>; Mon,  4 Sep 2017 11:42:58 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 325E661FA2; Mon,  4 Sep 2017 18:42:58 +0000 (UTC)
Message-ID: <59AD9EB2.4090505@redbarn.org>
Date: Mon, 04 Sep 2017 11:42:58 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
CC: "Walter H." <walter.h@mathemainzel.info>, dnsop WG <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org>
In-Reply-To: <20170904122222.C270F8413534@rock.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/c7Q8Dk1DLMrf9e3IoSnPri1CeyA>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 18:43:00 -0000

Mark Andrews wrote:
> In
> message<c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>,
> "Walter H." writes:
>> where there anyone who said: "don't use it", 15 years ago?
>
> Yes.  There were lots that discourage the use of .local, lan, .corp
> etc.  Just becaue you didn't hear from them doesn't mean they weren't
> out there.

alas, bad advice can circle the earth five times before the
countervailing good advice can get its shoes on.

-- 
P Vixie


From nobody Mon Sep  4 12:16:43 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76E4D126B6D for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 12:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 YGMQFZzVmtCW for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 12:16:39 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29B412421A for <dnsop@ietf.org>; Mon,  4 Sep 2017 12:16:39 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 23DE620C6C; Mon,  4 Sep 2017 15:16:39 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 04 Sep 2017 15:16:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=j0h3Bq2fEBuehWIZcRZxR2TFaWbdZHAs9rOwvsdY3gE=; b=qFYNzqJz ryFU/DCVZYBR6z2qFZUGeBk0ItHGm1B5kp4MsBWHIaH/pdtGrDw40Y/wuCl+24Xy v52C/P77Lfk4bo0yTVdKcOyi7ynx42oNQixUNndE2UxIWNN8hP1Z966n8MdfRMmt f+VDiQAPH8gdAqbATp0JvZkF2LXgSy0i8Q7cxVB1jUsGZg/VQHKxvpBgC5z7ifvH kMLlyDkHNRYZSOpvsUf8rbc1iLnMWNQhZUlsrivB6HKms/3BAfTtxT+ST2UV2Hst EpE2Wvsje36D0+PvMFNFLr3Z6V1BhRUnswtTVaNu0QRzEFBn2ApNMbvTwQIFWYgG TEJPnzneeMh9ww==
X-ME-Sender: <xms:l6atWcpO8e2hG5NwfpI6LZ_FrJlGJne2wJ_rspJc6zEndtAVpFmwSw>
X-Sasl-enc: JgZUmMEaMKjaEnWdvP61AUts0OVNgBR9QCbFhr7Byg7V 1504552598
Received: from [192.168.1.133] (unknown [195.147.34.210]) by mail.messagingengine.com (Postfix) with ESMTPA id CBC5F7F96B; Mon,  4 Sep 2017 15:16:38 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Tony Finch <dot@dotat.at>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>
Date: Mon, 4 Sep 2017 20:16:37 +0100
Cc: Mark Andrews <marka@isc.org>, dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>
To: "Walter H." <walter.h@mathemainzel.info>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wVb7l0uCNTzyNIG4SVcmAgN12vY>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 19:16:41 -0000

> On 4 Sep 2017, at 13:54, Walter H. <walter.h@mathemainzel.info> wrote:
>=20
> not really, at those days only a few TLDs where possible, the many TLDs ca=
me some years later ...

It should have been clear after 1997-1998 from the discussions of the IAHC a=
nd the setup of ICANN that there would be a lot more TLDs. It took a long ti=
me to ramp up but the process started more than 20 years ago.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at=


From nobody Mon Sep  4 12:30:03 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0694C126BF0 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 12:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 gGW-pNxS66Oq for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 12:30:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 903DB12421A for <dnsop@ietf.org>; Mon,  4 Sep 2017 12:30:00 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E381020BA2; Mon,  4 Sep 2017 15:29:59 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 04 Sep 2017 15:29:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=wA+6/+SZCyd2JT2D5Llw0836juvH/x9teBX3VamuImo=; b=abdcR2FF jtkTOuvWo69Es/0+X0XYy6vb5ShQNGFXV5FzeBahpr30DaLjQp3lOKUtqEsr8h5i IfXIUIE/nJBCykrGlV1d2ex+wGewMSrIciOQCQUHxBbqvmIDM2EZb0ZImaFETPV2 Ln/LZSSUopeAKZB+yA58E+72jox0IpxiHVz2/cu1WSVUInjaAtLyiU1PobEiJIML Cvqt+FePJ3MD4lLQYqTx5lBzoDrnTMvgQmtdcM4Fim0PJgUaz5GkF/VkpgOPsDrx EXRM2HWQBLJYEWBhuaZOm5VrDPbI4hZGNn8fiw+CpzrCMp5eJC3r4tweEN5MQCCH tyPZr2HfdSj8Dg==
X-ME-Sender: <xms:t6mtWbDEVqbudZzmCb2_pUhI9HCXry67DrQBGZnIyaPN825Jy0Zcfg>
X-Sasl-enc: V9goel5n0HsWujitBxO4bmOqE8JrB62CKqzO36hpq4/0 1504553399
Received: from [192.168.1.133] (unknown [195.147.34.210]) by mail.messagingengine.com (Postfix) with ESMTPA id 9715C7E954; Mon,  4 Sep 2017 15:29:59 -0400 (EDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-1E5C3CEB-4843-4507-BA2D-2ED072BE73A7
Mime-Version: 1.0 (1.0)
From: Tony Finch <dot@dotat.at>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org>
Date: Mon, 4 Sep 2017 20:29:57 +0100
Cc: Mark Andrews <marka@isc.org>, "Walter H." <Walter.H@mathemainzel.info>, "dnsop@ietf.org" <dnsop@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Haxpi5PMSsnUPqI-0Z6FjlmoF3I>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 19:30:02 -0000

--Apple-Mail-1E5C3CEB-4843-4507-BA2D-2ED072BE73A7
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable


> On 3 Sep 2017, at 22:51, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On 3 Sep 2017, at 14:38, Mark Andrews wrote:
>>=20
>>=20
>> Why would anyone tell you that =E2=80=9C.local=E2=80=9D would conflict wh=
en you were supposed
>> to register a name *before* using it.
>=20
> Because some vendors gave bad advice in their documentation, particularly i=
n examples.
>=20
>> If you are doing AD correctly you should be able to register you machines=
 wherever
>> they connect to the Internet and that requires a public registration.
>=20
> And that is what Microsoft has suggested in all their documentation for ma=
ny years.

However, Microsoft did encourage their customers to use .local names for Act=
ive Directory domains for quite a long time - see for example this link to t=
he documentation for Windows Small Business Server 2003. It isn't fair to on=
ly blame MS customers for choosing .local domains.

https://technet.microsoft.com/en-us/library/cc747455(v=3Dws.10).aspx

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at


--Apple-Mail-1E5C3CEB-4843-4507-BA2D-2ED072BE73A7
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div>On 3 Sep 2017, at 22:51=
, Paul Hoffman &lt;<a href=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@vpn=
c.org</a>&gt; wrote:<br></div><blockquote type=3D"cite"><span>On 3 Sep 2017,=
 at 14:38, Mark Andrews wrote:</span><blockquote type=3D"cite"><span></span>=
<br></blockquote><blockquote type=3D"cite"><span>Why would anyone tell you t=
hat =E2=80=9C.local=E2=80=9D would conflict when you were supposed</span><br=
></blockquote><blockquote type=3D"cite"><span>to register a name *before* us=
ing it.</span><br></blockquote><span></span><br><span>Because some vendors g=
ave bad advice in their documentation, particularly in examples.<br></span><=
span></span><br><blockquote type=3D"cite"><span>If you are doing AD correctl=
y you should be able to register you machines wherever</span><br></blockquot=
e><blockquote type=3D"cite"><span>they connect to the Internet and that requ=
ires a public registration.</span><br></blockquote><span></span><br><span>An=
d that is what Microsoft has suggested in all their documentation for many y=
ears.</span><br></blockquote><br><div>However, Microsoft did encourage their=
 customers to use .local names for Active Directory domains for quite a long=
 time - see for example this link to the documentation for Windows Small Bus=
iness Server 2003. It isn't fair to only blame MS customers for choosing .lo=
cal domains.</div><div><br></div><div><a href=3D"https://technet.microsoft.c=
om/en-us/library/cc747455(v=3Dws.10).aspx">https://technet.microsoft.com/en-=
us/library/cc747455(v=3Dws.10).aspx</a></div><div><br></div><div><div id=3D"=
AppleMailSignature"><span style=3D"background-color: rgba(255, 255, 255, 0);=
">Tony.</span><div><span style=3D"background-color: rgba(255, 255, 255, 0);"=
>--&nbsp;</span></div><div><span style=3D"background-color: rgba(255, 255, 2=
55, 0);">f.anthony.n.finch &nbsp;&lt;<a href=3D"mailto:dot@dotat.at">dot@dot=
at.at</a>&gt; &nbsp;<a href=3D"http://dotat.at">http://dotat.at</a></span></=
div></div><div><br></div></div></body></html>=

--Apple-Mail-1E5C3CEB-4843-4507-BA2D-2ED072BE73A7--


From nobody Mon Sep  4 13:45:58 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF6F112422F for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 13:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 EMNUmjcfqQ3R for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 13:45:55 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721F9120721 for <dnsop@ietf.org>; Mon,  4 Sep 2017 13:45:55 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 197AE3493BB; Mon,  4 Sep 2017 20:45:53 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D1D5116005C; Mon,  4 Sep 2017 20:45:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 96F6616007F; Mon,  4 Sep 2017 20:45:52 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DonGJSiaXdvB; Mon,  4 Sep 2017 20:45:52 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 03F1B16005C; Mon,  4 Sep 2017 20:45:52 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id A05018415E35; Tue,  5 Sep 2017 06:45:49 +1000 (AEST)
To: "Walter H." <walter.h@mathemainzel.info>
Cc: "Jim Reid" <jim@rfc1035.com>, "dnsop WG" <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>
In-reply-to: Your message of "Mon, 04 Sep 2017 14:54:39 +0200." <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>
Date: Tue, 05 Sep 2017 06:45:49 +1000
Message-Id: <20170904204549.A05018415E35@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2HmJWaFaa_X2eLH11zB1KXB6Ulc>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 20:45:57 -0000

In message <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>, "Walter
 H." writes:
> On Mon, September 4, 2017 14:22, Mark Andrews wrote:
> >
> > In message <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>,
> > "Walter H." writes:
> >> where there anyone who said: "don't use it", 15 years ago?
> >
> > Yes.  There were lots that discourage the use of .local, lan,
> > .corp etc.  Just becaue you didn't hear from them doesn't mean
> > they weren't out there.
> 
> a discourage is not a "don't use" :-)

We gave them fair warning that and domain they choose could be
allocated in the future.  We told them to the advice you have been
getting today.  Use a zone registered to them.  They, like you are
today, are ignoring the advice.

> >> > 'home.arpa' is in the process of being registered so that it
> >> > can be used safely in the environment it is designed to be used in.
> >>
> >> yes, but commonly for residental networks, not company/enterprise
> >> networks,
> >> they want/need something shorter like ".corp", ".lan", ".local", ...
> >
> > Want maybe, need absolutely not.
> question: why isn't this the answer of a car dealer?

Because the car dealer is trying to take as much money off you as
they can.  We on the other hand are trying to save you money by
stopping you and everyone else getting into situations that will
cost you/them thousands of dollars to rectify in the future.

> > Everyone was told to register the domain you want to use, there was
> > no exception for active directory.
> 
> not really, at those days only a few TLDs where possible, the many TLDs
> came some years later ...

People were wanting to deploy more TLDs from the moment the Internet
was opened up to the public.

> by the way: where is the problem with .home or .corp?
> I ask this, because at my hoster I pre-reserved my "local domain" - a
> .home, that I have used for many years several zears ago and nothing
> happened ...
> 
> > IPv6 would have been deployed a lot sooner. :-)
> 
> not really, my ISP is still IPv4 only ..., my IPv6 connectivity is a
> HE-tunnel ...
> and the brand new OS from Microsoft still has the bugs inside: TEREDO, ...
> which I had to deactivate first, before it is usable with IPv6 at all ...

If you didn't have the relief valve of RFC 1918 addresses then yes
IPv6 would have come a lot quicker and stuff like TEREDO wouldn't
exist.

> > Except such systems exist.  Go look at what a Mac does.  ping for
> > test.local and look and port 5353 traffic and compare it to port 53
> > traffic.
> 
> I know, this RFC was written by Apple;
> 
> no Apple no problem, I would say :-)
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 14:40:00 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8D013213D for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 14:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 V1EkxqZStntv for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 14:39:58 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BBB4132139 for <dnsop@ietf.org>; Mon,  4 Sep 2017 14:39:58 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc] (unknown [IPv6:2001:559:8000:c9:dc3:59e3:1fa5:69dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 754EE61FA2; Mon,  4 Sep 2017 21:39:57 +0000 (UTC)
Message-ID: <59ADC82E.8000306@redbarn.org>
Date: Mon, 04 Sep 2017 14:39:58 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: "Walter H." <walter.h@mathemainzel.info>, dnsop WG <dnsop@ietf.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at>
In-Reply-To: <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rueHB1vq4J42pDiA1ZzjoOcolbo>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 21:39:59 -0000

Tony Finch wrote:
> It should have been clear after 1997-1998 from the discussions of the
> IAHC and the setup of ICANN that there would be a lot more TLDs. It
> took a long time to ramp up but the process started more than 20
> years ago.

money changes everything.

-- 
P Vixie


From nobody Mon Sep  4 15:18:01 2017
Return-Path: <mhw@wittsend.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57BFE13219B for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.091
X-Spam-Level: 
X-Spam-Status: No, score=-1.091 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_PASS=-0.001, T_TVD_MIME_EPI=0.01] autolearn=no autolearn_force=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 bd5qlBsvaPNp for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:17:54 -0700 (PDT)
Received: from wittsend.com (romulus.wittsend.com [130.205.32.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65144132199 for <dnsop@ietf.org>; Mon,  4 Sep 2017 15:17:54 -0700 (PDT)
Received: from canyon.ip6.wittsend.com (canyon.ip6.wittsend.com [IPv6:2001:470:8:a48:3e97:eff:fe4d:9bc7]) (authenticated bits=0) by wittsend.com (8.15.2/8.15.2) with ESMTPSA id v84MHarx013790 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Sep 2017 18:17:37 -0400
Message-ID: <1504563125.29012.4.camel@WittsEnd.com>
From: "Michael H. Warfield" <mhw@wittsend.com>
Reply-To: mhw@wittsend.com
To: Tony Finch <dot@dotat.at>, Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "Michael H.Warfield" <mhw@WittsEnd.com>, "dnsop@ietf.org" <dnsop@ietf.org>, "Walter H." <Walter.H@mathemainzel.info>
Date: Mon, 04 Sep 2017 18:12:05 -0400
In-Reply-To: <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at>
Organization: Thaumaturgy & Speculums Technology
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-ZipFJ/nkd/VaMcGMzU3y"
X-Mailer: Evolution 3.24.5 (3.24.5-1.fc26) 
Mime-Version: 1.0
X-WittsEnd-MailScanner-Information: Please contact the ISP for more information
X-WittsEnd-MailScanner-ID: v84MHarx013790
X-WittsEnd-MailScanner: Found to be clean
X-WittsEnd-MailScanner-From: mhw@wittsend.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/g87gOxYmjN33dIhRlH9pGFqNpTY>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 22:17:58 -0000

--=-ZipFJ/nkd/VaMcGMzU3y
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2017-09-04 at 20:29 +0100, Tony Finch wrote:
>=20
> On 3 Sep 2017, at 22:51, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> > On 3 Sep 2017, at 14:38, Mark Andrews wrote:
> > > Why would anyone tell you that =E2=80=9C.local=E2=80=9D would conflic=
t when you
> > > were supposed
> > > to register a name *before* using it.
> >=20
> > Because some vendors gave bad advice in their documentation,
> > particularly in examples.
> >=20
> > > If you are doing AD correctly you should be able to register you
> > > machines wherever
> > > they connect to the Internet and that requires a public
> > > registration.
> >=20
> > And that is what Microsoft has suggested in all their documentation
> > for many years.

> However, Microsoft did encourage their customers to use .local names
> for Active Directory domains for quite a long time - see for example
> this link to the documentation for Windows Small Business Server
> 2003. It isn't fair to only blame MS customers for choosing .local
> domains.

> https://technet.microsoft.com/en-us/library/cc747455(v=3Dws.10).aspx

I would point out an analogous situation with documentation and
addresses.  The documentation that accompanied Sun Microsystems SunOS
and Solaris used examples of IP address 1.1.1.1 and 1.2.3.4 and
similar, now making those blocks toxic since that /8 was assigned to
APNIC.  IIRC, they also used names like .local and .test in some of
their doco.  This isn't just a Microsoft think (and I'm far FAR from a
Microsoft apologist).  Sometimes our tech writers do things they
shouldn't when their crystal ball is cloud and we get stuck with the
results.  And I've dealt with far FAR worse.

> Tony.
> --=20
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at

Regards,
Mike
--=20
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  mhw@WittsEnd.com
   /\/\|=3Dmhw=3D|\/\/          | (c) +1 678 463-0932 |  http://www.wittsen=
d.com/mhw/
ARIN whois: ARIN-MHW9       | An optimist believes we live in the best of a=
ll
PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!

--=-ZipFJ/nkd/VaMcGMzU3y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEVg8QRvd9/qpgX3lAwOuWdWdGJ/8FAlmtz7YACgkQwOuWdWdG
J//OkQgAzOQANaXYM8meSzAZYZMAU1aErfrHL2884LoTLxKwpmM7/bYMQh/eroj4
xNeZU8fA2ECcx54RezC1WRHaQOUrnkMxU5y5rdcf97wxqGA4+8NZCkRVyIvxkEVC
hmEN/5nZ4KyicoJYWdb5z8ryFWfBhJAaBY0C1fUMLpsprCTQTtIaEylXO9362USZ
WGLpw36zMkEdLybCvd+AlNbNcUB6BUDSYaibK3p6BzTHSh4+EgobaVr/VTPaZTIB
C1FRZpIok44+UA7O3l74dc8ExmgSt7iw2ztRP6u8kc6K77tvURYXYM/NcFwApTQY
TD3E5BySYtwCYyL4lKB7/SjpD/gPGA==
=2BzR
-----END PGP SIGNATURE-----

--=-ZipFJ/nkd/VaMcGMzU3y--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From nobody Mon Sep  4 15:22:45 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D4913219C for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 wG8K7ne5_Eya for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:22:42 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBD9113219B for <dnsop@ietf.org>; Mon,  4 Sep 2017 15:22:41 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v84MMeHD029811 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Sep 2017 15:22:41 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <1504563125.29012.4.camel@WittsEnd.com>
Date: Mon, 4 Sep 2017 15:22:35 -0700
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <88921B49-3909-4255-9E8B-FAE25F81EDC8@orthanc.ca>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com>
To: mhw@wittsend.com
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eHTWxcfdFrImQOhPDyv-Sf4A26M>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 22:22:43 -0000

> On Sep 4, 2017, at 3:12 PM, Michael H. Warfield <mhw@wittsend.com> =
wrote:
>=20
> I would point out an analogous situation with documentation and
> addresses.  The documentation that accompanied Sun Microsystems SunOS
> and Solaris used examples of IP address 1.1.1.1 and 1.2.3.4 and
> similar, now making those blocks toxic since that /8 was assigned to
> APNIC.  IIRC, they also used names like .local and .test in some of
> their doco.  This isn't just a Microsoft think (and I'm far FAR from a
> Microsoft apologist).  Sometimes our tech writers do things they
> shouldn't when their crystal ball is cloud and we get stuck with the
> results.  And I've dealt with far FAR worse.

Wasn't 192.9.200 (from the Sun docs) the "1918" network of the =
mid-1980s?  I also recall SunOS manuals from that era encouraging =
customers to contact SMI if they needed a class C network block.

--lyndon


From nobody Mon Sep  4 15:43:47 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 506C5132193 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 sQQ_zQexYBSs for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 15:43:44 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 387D1132192 for <dnsop@ietf.org>; Mon,  4 Sep 2017 15:43:44 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 17F7624AE10; Mon,  4 Sep 2017 22:42:16 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9673716005C; Mon,  4 Sep 2017 22:42:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4C51F16007F; Mon,  4 Sep 2017 22:42:22 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id r6Myjbclv2aV; Mon,  4 Sep 2017 22:42:22 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 9037B16005C; Mon,  4 Sep 2017 22:42:21 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D6ED78419425; Tue,  5 Sep 2017 08:42:18 +1000 (AEST)
To: mhw@wittsend.com
Cc: Tony Finch <dot@dotat.at>, Paul Hoffman <paul.hoffman@vpnc.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "Walter H." <Walter.H@mathemainzel.info>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com>
In-reply-to: Your message of "Mon, 04 Sep 2017 18:12:05 -0400." <1504563125.29012.4.camel@WittsEnd.com>
Date: Tue, 05 Sep 2017 08:42:18 +1000
Message-Id: <20170904224218.D6ED78419425@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BBTfJs60kFHv3ypC0KUdSSM_6Zg>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 22:43:46 -0000

In message <1504563125.29012.4.camel@WittsEnd.com>, "Michael H. Warfield" write
s:
> On Mon, 2017-09-04 at 20:29 +0100, Tony Finch wrote:
> >
> > On 3 Sep 2017, at 22:51, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> > > On 3 Sep 2017, at 14:38, Mark Andrews wrote:
> > > > Why would anyone tell you that “.local” would conflict when you
> > > > were supposed
> > > > to register a name *before* using it.
> > >
> > > Because some vendors gave bad advice in their documentation,
> > > particularly in examples.
> > >
> > > > If you are doing AD correctly you should be able to register you
> > > > machines wherever
> > > > they connect to the Internet and that requires a public
> > > > registration.
> > >
> > > And that is what Microsoft has suggested in all their documentation
> > > for many years.
>
> > However, Microsoft did encourage their customers to use .local names
> > for Active Directory domains for quite a long time - see for example
> > this link to the documentation for Windows Small Business Server
> > 2003. It isn't fair to only blame MS customers for choosing .local
> > domains.
>
> > https://technet.microsoft.com/en-us/library/cc747455(v=ws.10).aspx
>
> I would point out an analogous situation with documentation and
> addresses.  The documentation that accompanied Sun Microsystems SunOS
> and Solaris used examples of IP address 1.1.1.1 and 1.2.3.4 and
> similar, now making those blocks toxic since that /8 was assigned to
> APNIC.  IIRC, they also used names like .local and .test in some of
> their doco.  This isn't just a Microsoft think (and I'm far FAR from a
> Microsoft apologist).  Sometimes our tech writers do things they
> shouldn't when their crystal ball is cloud and we get stuck with the
> results.  And I've dealt with far FAR worse.

The keyword above was examples which they clearly were.  Most of
1.0.0.0/8 is in use today despite those examples.  The use of local
test were also clearly examples.  The Microsoft page above advocated
the use literal use of .local which is very different.

APNIC could allocate those addresses if they wished without much
issues.  I'm sure there would be lots of takers even given the known
limitations.  There would be a little extra traffic.  They are
perfect for eyeball only usage.  The real issues arise if you try
to use those addresses for servers.

Mark

> > Tony.
> > --
> > f.anthony.n.finch  <dot@dotat.at>  http://dotat.at
>
> Regards,
> Mike
> --
> Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 |  mhw@WittsEnd.com
>    /\/\|=mhw=|\/\/          | (c) +1 678 463-0932 |
> http://www.wittsend.com/mhw/
> ARIN whois: ARIN-MHW9       | An optimist believes we live in the best of
> all
> PGP Key: 0xC0EB9675674627FF | possible worlds.  A pessimist is sure of it!

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 16:02:27 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9ADD132193 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 16:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 9t6_GD2YTEbD for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 16:02:24 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A7AB132192 for <dnsop@ietf.org>; Mon,  4 Sep 2017 16:02:24 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 82A4A20BD9; Mon,  4 Sep 2017 19:02:23 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 04 Sep 2017 19:02:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=OoU8u9g/0HM5dl4AeGNBSWn9QwdN/LUDSO3eRTnofwo=; b=IwT8WGtf I50XldjjAjvx5pq1uiiPTe82qzZurCLMujQDUn/XAsZolNWOQyUcGweX5+tKTIJH U/g14wml3dO6I5z7+7Ldmqu10IgILGTpCimfOuZthzvN0gusHP7rsmzmtsVhO7nf iWKp9eudJP8zSHXSg6PJOESjjRo73swqPc2aeFkALYBYlJU7NPByX6Ect9olJhOY O0vnVROpuRz4PKY278lqfA+AktvwA4waYy7MVYUkhye0d+ECuDuGoobUl0F61pjv ihLwvkywON/jOCnIk9aeLRygp0VyXqMFr9s9K5oHd9TqgRAiCZDIRo1/iU0r3pcP X5ds2oZ23+8n7w==
X-ME-Sender: <xms:f9utWWvk3IGZJ4Lw93t5TNuYu3i-7LiIK9agjAGWP-0vNXKhlUUJ9w>
X-Sasl-enc: v6m5AmltSKgasqDvSdQlzlbczBGuA2B6FtcwLtMMNNKs 1504566143
Received: from [192.168.1.133] (unknown [195.147.34.210]) by mail.messagingengine.com (Postfix) with ESMTPA id 32FA27E692; Mon,  4 Sep 2017 19:02:23 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Tony Finch <dot@dotat.at>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <20170904224218.D6ED78419425@rock.dv.isc.org>
Date: Tue, 5 Sep 2017 00:02:21 +0100
Cc: mhw@wittsend.com, Paul Hoffman <paul.hoffman@vpnc.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "Walter H." <Walter.H@mathemainzel.info>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F32B3A51-33B4-4E69-852E-5B60B85D3961@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com> <20170904224218.D6ED78419425@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/L2JZtLDod473Tjxn8aj411cMc4U>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 23:02:26 -0000

> On 4 Sep 2017, at 23:42, Mark Andrews <marka@isc.org> wrote:
>>=20
>>> https://technet.microsoft.com/en-us/library/cc747455(v=3Dws.10).aspx
>=20
> The Microsoft page above advocated
> the use literal use of .local which is very different.

Worse than that! It was the default suggested by the software!

I think this dated from the late 1990s when registering domain names was qui=
te expensive and inconvenient, so I can see why they did it. A better altern=
ative would have been to make the default parent domain something registered=
 by MS, instead of a fake TLD.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at



From nobody Mon Sep  4 20:53:55 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9EE1321D5 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 20:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 HRi3fVr-s331 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 20:53:52 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0111241F3 for <dnsop@ietf.org>; Mon,  4 Sep 2017 20:53:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=Ce9sJO7kXTtTjsXpoCxjTkN1Fo8RunTsMNuz1iAXzA4=;  b=g3N3fd1kQoAvqSsQC4QIfI+f43zda+HfXkBHbfYxNBLjMqjUwoZbxwwYzCG8sxo7iG0y6WL4hC6nfURPJCtvQnBiZsTUzPrYVeuGvU2OIBQkaFXU7p9fP17HYzFqdbboIouy481v1B405OGizQwimOHWyN4xkYLuh36jNCCiZks=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp4vs-0001kq-Np; Tue, 05 Sep 2017 05:53:48 +0200
Message-ID: <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail>
In-Reply-To: <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at>
Date: Tue, 5 Sep 2017 05:53:47 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Tony Finch" <dot@dotat.at>
Cc: "Walter H." <walter.h@mathemainzel.info>, "Mark Andrews" <marka@isc.org>,  "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lCch_BdPny0l0Wn5v0DNfHtSPqs>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 03:53:54 -0000

On Mon, September 4, 2017 21:16, Tony Finch wrote:
>
>> On 4 Sep 2017, at 13:54, Walter H. <walter.h@mathemainzel.info> wrote:
>>
>> not really, at those days only a few TLDs where possible, the many TLDs
>> came some years later ...
>
> It should have been clear after 1997-1998 from the discussions of the IAHC
> and the setup of ICANN that there would be a lot more TLDs.

"would" is fiction ...



From nobody Mon Sep  4 20:56:17 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CC41241F3 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 20:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 ddMvofzvenzv for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 20:56:15 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C5381321ED for <dnsop@ietf.org>; Mon,  4 Sep 2017 20:56:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=coX1zHIBTnnvc8TiBoSvBNW2KTlCuCF63iIfPjhHSbE=;  b=suwdbPIdlrPBkeog4WNm7/0UjuWspEL9/wsUhM+GzuKSqYBdb8VlXCQRQlG2/ujllPGl5qcpeihk2BL0AE96jnq3+gi/T5HORGESbSPzVysS7X2gfPTWPJ2F72nkZrmLe84vfKh3Pd+OmwCq6WpXWi7NnS3GExab4WNUSYWn+D4=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp4yD-00026o-6h; Tue, 05 Sep 2017 05:56:13 +0200
Message-ID: <a1194496d3086f9391ff6986ae7fba26.1504583772@squirrel.mail>
In-Reply-To: <20170904204549.A05018415E35@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <20170904204549.A05018415E35@rock.dv.isc.org>
Date: Tue, 5 Sep 2017 05:56:12 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: "Walter H." <walter.h@mathemainzel.info>, "Jim Reid" <jim@rfc1035.com>, "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/A4usqsgIYv8ukHc9dMTiYxR4rjY>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 03:56:16 -0000

On Mon, September 4, 2017 22:45, Mark Andrews wrote:
>
>> >> > 'home.arpa' is in the process of being registered so that it
>> >> > can be used safely in the environment it is designed to be used in.
>> >>
>> >> yes, but commonly for residental networks, not company/enterprise
>> >> networks,
>> >> they want/need something shorter like ".corp", ".lan", ".local", ...
>> >
>> > Want maybe, need absolutely not.
>> question: why isn't this the answer of a car dealer?
>
> Because the car dealer is trying to take as much money off you as
> they can.

and the registries are for free?



From nobody Mon Sep  4 21:01:58 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6A51321F1 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 5CVFQYh3E66m for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:01:55 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F4091321ED for <dnsop@ietf.org>; Mon,  4 Sep 2017 21:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=H/q3dygCm6Vjfeobl4TX+hagtffyEILfflb7DI5BHmE=;  b=kxhtrvEWAIy0HWm1Fd59QOFdLs5k8D/2Q3MSyQrWK/L32Eg/11cX9wmK/C9/0/myJ7qH8jSOh3VqCRRIZX4jF4518aEQIvFL8xzLSOFpWPX1OPetd0mBlYqTHBUsHrq/+9M20FywSNytLxO74Q1215tMgAn+Q3XS58DlNZYYAr8=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp53h-0002xw-A0; Tue, 05 Sep 2017 06:01:53 +0200
Message-ID: <b9a35d8e8ccc2f6e0e2d15b112bd32b8.1504584112@squirrel.mail>
In-Reply-To: <20170904224218.D6ED78419425@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com> <20170904224218.D6ED78419425@rock.dv.isc.org>
Date: Tue, 5 Sep 2017 06:01:52 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: mhw@wittsend.com, "Tony Finch" <dot@dotat.at>, "Paul Hoffman" <paul.hoffman@vpnc.org>, "dnsop@ietf.org" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/85hvkiUYBTPD2JSkXJmQW07FO6c>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:01:56 -0000

> The keyword above was examples which they clearly were.  Most of
> 1.0.0.0/8 is in use today despite those examples.  The use of local
> test were also clearly examples.  The Microsoft page above advocated
> the use literal use of .local which is very different.

and now in the IPv6 ages the same bug is done again ...

2001:db8: ...




From nobody Mon Sep  4 21:04:15 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2092913232C for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 oQkRqyQAKVqk for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:04:12 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9392E1321F1 for <dnsop@ietf.org>; Mon,  4 Sep 2017 21:04:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=nZxO00TCY1i50Nbe4HHMLMN8Fsn7fCwLT12RaaB12zU=;  b=Z5Ao/hXQMw9YBQ9EhCqjcBzcPNmKrVSSgRxMjDMGyd53Arry7HBy31do4n/9Q0uelUISvQU+Ochj1IOLrZX+roH3kssufhdSBdGcdNU19+I6cPS5ha8oybvX5qIXm5iGn+VgQAhsiEoDat6qLCuXrJ0wKjUnYb7f47lsMLY9wYk=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp55p-0003Mw-0g; Tue, 05 Sep 2017 06:04:05 +0200
Message-ID: <4285563a2c00895789eba3c9aa2be4e1.1504584244@squirrel.mail>
In-Reply-To: <F32B3A51-33B4-4E69-852E-5B60B85D3961@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com> <20170904224218.D6ED78419425@rock.dv.isc.org> <F32B3A51-33B4-4E69-852E-5B60B85D3961@dotat.at>
Date: Tue, 5 Sep 2017 06:04:04 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Tony Finch" <dot@dotat.at>
Cc: "Mark Andrews" <marka@isc.org>, mhw@wittsend.com, "Paul Hoffman" <paul.hoffman@vpnc.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "Walter H." <walter.h@mathemainzel.info>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kL9kD20eqhc0qwT2_PRM7bl4aJQ>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:04:13 -0000

On Tue, September 5, 2017 01:02, Tony Finch wrote:
>
> A better
> alternative would have been to make the default parent domain something
> registered by MS, instead of a fake TLD.

yes and no;  I still don't have "my" .home even I pre-registered it
several years ago ...


From nobody Mon Sep  4 21:09:12 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDAE71321A5 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 6kVugoAPJQFc for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:09:09 -0700 (PDT)
Received: from mx17lb.world4you.com (mx17lb.world4you.com [81.19.149.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797AC1241F3 for <dnsop@ietf.org>; Mon,  4 Sep 2017 21:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=mwDAaicq9JnNWGyGWk4rgSbAKaqfUfR2qvDtqX4eY/8=;  b=wlv+QfAA5vH7nk5rwyhN5fWfPbRx3gWqWgn1wVbM9+qOJK2pSkq6rcI5M4I4xnAaUsqfLvcmvWdvpK8cPUAMUAg0Ru0PfB50UgGVDEy9IdCtvJUKOkbeGYvAEE5hGE+acnKPOz0y/cG46pbQOHa+WTHLTNWLrnWFmwQJm/m9TMw=;
Received: from [90.146.55.206] (helo=home.mail) by mx17lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp5Ah-0004ME-Uo; Tue, 05 Sep 2017 06:09:07 +0200
Message-ID: <d36b860a6bc8b42fbb1ba3bf3f4ce03a.1504584546@squirrel.mail>
In-Reply-To: <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at>
Date: Tue, 5 Sep 2017 06:09:06 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Tony Finch" <dot@dotat.at>
Cc: "Paul Hoffman" <paul.hoffman@vpnc.org>, "Mark Andrews" <marka@isc.org>, "Walter H." <walter.h@mathemainzel.info>, "dnsop@ietf.org" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx17lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/08nJEZREQ0YFU6oKRmoyQO584ew>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:09:11 -0000

On Mon, September 4, 2017 21:29, Tony Finch wrote:
>
> However, Microsoft did encourage their customers to use .local names for
> Active Directory domains for quite a long time - see for example this link
> to the documentation for Windows Small Business Server 2003. It isn't fair
> to only blame MS customers for choosing .local domains.
>
> https://technet.microsoft.com/en-us/library/cc747455(v=ws.10).aspx

I see it exact this, and it would be fair to prevent future bugs with
defining one or two FAKE TLDs (e.g. .corp, .lan) for exact this use case;

as I said there are 2 points:
- there isn't really a uniqness as requirement
- a public WHOIS grabbing for these domains needn't also be given;


From nobody Mon Sep  4 21:34:41 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0881321F1 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 4fafAxgeo2TF for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:34:38 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8338B1241F3 for <dnsop@ietf.org>; Mon,  4 Sep 2017 21:34:38 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 5F80B34AE4C; Tue,  5 Sep 2017 04:34:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 4C01C16005C; Tue,  5 Sep 2017 04:34:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5095C160067; Tue,  5 Sep 2017 04:34:32 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ld76PjZtxTCk; Tue,  5 Sep 2017 04:34:32 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 0068B16005C; Tue,  5 Sep 2017 04:34:31 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 811BF8436B95; Tue,  5 Sep 2017 14:34:29 +1000 (AEST)
To: "Walter H." <walter.h@mathemainzel.info>
Cc: "Tony Finch" <dot@dotat.at>, "dnsop WG" <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at> <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail>
In-reply-to: Your message of "Tue, 05 Sep 2017 05:53:47 +0200." <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail>
Date: Tue, 05 Sep 2017 14:34:29 +1000
Message-Id: <20170905043429.811BF8436B95@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2lBblteCtIJszTDMY_7ZOJ68opc>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:34:40 -0000

In message <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail>, "Walter
 H." writes:
> On Mon, September 4, 2017 21:16, Tony Finch wrote:
> >
> >> On 4 Sep 2017, at 13:54, Walter H. <walter.h@mathemainzel.info> wrote:
> >>
> >> not really, at those days only a few TLDs where possible, the many TLDs
> >> came some years later ...
> >
> > It should have been clear after 1997-1998 from the discussions of the IAHC
> > and the setup of ICANN that there would be a lot more TLDs.
> 
> "would" is fiction ...

Yes, it was clear that there would be more TLD's then even if most
of them would be run by speculators and would provide little benefit.
This was a little before Jon's death in 1998.  I remember having
lunch with him and thinking about this issue over lunch.

Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Sep  4 21:46:42 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F22DC1321A5 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 RdcQO5POjLC9 for <dnsop@ietfa.amsl.com>; Mon,  4 Sep 2017 21:46:38 -0700 (PDT)
Received: from mx07lb.world4you.com (mx07lb.world4you.com [81.19.149.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A3D1241F3 for <dnsop@ietf.org>; Mon,  4 Sep 2017 21:46:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=57+TZ7LKlljoM63vLzyz2NlyHZEvDu77lgzrldTaKsk=;  b=QB+3ismROre/hRLqxZi2ACYdCe66Lvv/XB7gBlGQN5pjH/af6rAoXDREs88HjgFrW1zdPZdC5VdoGiDCXLZxZ4jQl4Cu+y+JrC/IhdAccMkPj0olJM1qQaIg1E0+i1d0mVaGM2SV884EzSRbKNI6/JWDPJhLNHFIB+y2MIU4dVA=;
Received: from [90.146.55.206] (helo=home.mail) by mx07lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp5ky-0000u1-BO; Tue, 05 Sep 2017 06:46:36 +0200
Message-ID: <c4cf90cddb0c88be4c896766c6d2548e.1504586795@squirrel.mail>
In-Reply-To: <20170905043429.811BF8436B95@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <8D745760-633D-4FDC-BEE0-3DF1DF6408ED@dotat.at> <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail> <20170905043429.811BF8436B95@rock.dv.isc.org>
Date: Tue, 5 Sep 2017 06:46:35 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Mark Andrews" <marka@isc.org>
Cc: "Walter H." <walter.h@mathemainzel.info>, "Tony Finch" <dot@dotat.at>, "dnsop WG" <dnsop@ietf.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx07lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xeIvuZhIKLt9Is-Bp9d08fgD2bE>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:46:40 -0000

On Tue, September 5, 2017 06:34, Mark Andrews wrote:
>
> In message <d89eeb731eee3ff36bf5035231c0c810.1504583627@squirrel.mail>,
> "Walter
>  H." writes:
>> On Mon, September 4, 2017 21:16, Tony Finch wrote:
>> >
>> >> On 4 Sep 2017, at 13:54, Walter H. <walter.h@mathemainzel.info>
>> wrote:
>> >>
>> >> not really, at those days only a few TLDs where possible, the many
>> TLDs
>> >> came some years later ...
>> >
>> > It should have been clear after 1997-1998 from the discussions of the
>> IAHC
>> > and the setup of ICANN that there would be a lot more TLDs.
>>
>> "would" is fiction ...
>
> Yes, it was clear that there would be more TLD's then even if most
> of them would be run by speculators and would provide little benefit.

as I said "would" is fiction, and not real, so these didn't help anything ...

> This was a little before Jon's death in 1998.

I know Mr. "RFC-Editor"

> I remember having
> lunch with him and thinking about this issue over lunch.

and nothing happened ...


From nobody Tue Sep  5 00:04:34 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9005E13240D for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 00:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 CQ-qga4pSnsi for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 00:04:31 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B03C120727 for <dnsop@ietf.org>; Tue,  5 Sep 2017 00:04:31 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 4017428067C; Tue,  5 Sep 2017 09:04:29 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 399D5280692; Tue,  5 Sep 2017 09:04:29 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 3293428067C; Tue,  5 Sep 2017 09:04:29 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 2F8AC606D941; Tue,  5 Sep 2017 09:04:29 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 2352A3FFBF; Tue,  5 Sep 2017 09:04:29 +0200 (CEST)
Date: Tue, 5 Sep 2017 09:04:29 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Walter H." <walter.h@mathemainzel.info>
Cc: Tony Finch <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20170905070429.pjoygae5ju63ylri@nic.fr>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <d36b860a6bc8b42fbb1ba3bf3f4ce03a.1504584546@squirrel.mail>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d36b860a6bc8b42fbb1ba3bf3f4ce03a.1504584546@squirrel.mail>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000077, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.5.65716
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hXQaqlV78IwEiS6meciltQQJQ8w>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 07:04:33 -0000

On Tue, Sep 05, 2017 at 06:09:06AM +0200,
 Walter H. <walter.h@mathemainzel.info> wrote 
 a message of 20 lines which said:

> I see it exact this, and it would be fair to prevent future bugs with
> defining one or two FAKE TLDs (e.g. .corp, .lan) for exact this use
> case;

Why does it need to be a TLD (see all the discussions here about
Special Use Domain Names, .alt, .alt.arpa, etc)? Why not
lan.mycompany.com?

> - there isn't really a uniqness as requirement

As I said before, and explained, you're wrong here, since you don't
take merging and acquisition into account.

> - a public WHOIS grabbing for these domains needn't also be given;

With a subdomain of your Second Level Domain, no need for WHOIS (or
RDAP).

But I agree that ICANN rules for the .corp TLDs are stupid. If
McDonald's register .MCDONALDS, why do they need delegation and public
social info for the SLD?


From nobody Tue Sep  5 01:15:05 2017
Return-Path: <walter.h@mathemainzel.info>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAC132644 for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 01:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mathemainzel.info
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 ji8jmOEXY90h for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 01:15:00 -0700 (PDT)
Received: from mx05lb.world4you.com (mx05lb.world4you.com [81.19.149.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8294132396 for <dnsop@ietf.org>; Tue,  5 Sep 2017 01:15:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mathemainzel.info; s=dkim11;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=IJCekTceJN2NvGU59AVPPbxizcWCO5E1qST7fkKnYao=;  b=NcK4KpyzYhtARZC9hEe5yUfNSmhiWiyNEGEGkvPEeNQ8ziibiPBJofLBNcvUh5ZmTSrvlRViqY8h9l/GavYYAnKKy6IDQUli8d64GciTs99lVVypDOjilCvzKFpm/UKN5zKDHpkipeMQhiooS9rTOeO27fMsTF2Nk1pr0W+KOlc=;
Received: from [90.146.55.206] (helo=home.mail) by mx05lb.world4you.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <walter.h@mathemainzel.info>) id 1dp90c-0001lh-7u; Tue, 05 Sep 2017 10:14:58 +0200
Message-ID: <8a319a43de6437ee6c9d366a707efc83.1504599297@squirrel.mail>
In-Reply-To: <20170905070429.pjoygae5ju63ylri@nic.fr>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <d36b860a6bc8b42fbb1ba3bf3f4ce03a.1504584546@squirrel.mail> <20170905070429.pjoygae5ju63ylri@nic.fr>
Date: Tue, 5 Sep 2017 10:14:57 +0200
From: "Walter H." <walter.h@mathemainzel.info>
To: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
Cc: "Walter H." <walter.h@mathemainzel.info>, "Tony Finch" <dot@dotat.at>, "dnsop@ietf.org" <dnsop@ietf.org>, "Paul Hoffman" <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (UNIX; U; Cray X-MP/48; en-US; rv:2.70) Gecko/20110929 Communicator/7.20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Do-Not-Run: Yes
X-AV-Do-Run: Yes
X-SA-Exim-Connect-IP: 90.146.55.206
X-SA-Exim-Mail-From: walter.h@mathemainzel.info
X-SA-Exim-Scanned: No (on mx05lb.world4you.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QP5IaZBP7oyzm9qW64mRRVkKg-o>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 08:15:04 -0000

On Tue, September 5, 2017 09:04, Stephane Bortzmeyer wrote:
> On Tue, Sep 05, 2017 at 06:09:06AM +0200,
>  Walter H. <walter.h@mathemainzel.info> wrote
>  a message of 20 lines which said:
>
>> I see it exact this, and it would be fair to prevent future bugs with
>> defining one or two FAKE TLDs (e.g. .corp, .lan) for exact this use
>> case;
>
> Why does it need to be a TLD (see all the discussions here about
> Special Use Domain Names, .alt, .alt.arpa, etc)?

.alt is a TLD ...

> Why not lan.mycompany.com?

because mycompany.com is in WHOIS ..., see below

>> - there isn't really a uniqness as requirement
>
> As I said before, and explained, you're wrong here,

no, because nobody said, that uniqness is forbidden ..., and uniqness
implicitly requires the other point which I'd say, that MUST NOT

>> - a public WHOIS grabbing for these domains needn't also be given;
>
> With a subdomain of your Second Level Domain, no need for WHOIS (or
> RDAP).

you are wrong ...
the subdomain is part of the Second Level Domain and so there is a need
for WHOIS (or RDAP) for the Second Level Domain ...



From nobody Tue Sep  5 06:46:00 2017
Return-Path: <matt@conundrum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 731C6132C3F for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 06:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.com
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 g4YbRP-iJWND for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 06:45:56 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1707132C2B for <dnsop@ietf.org>; Tue,  5 Sep 2017 06:45:56 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id q64so16359260iod.5 for <dnsop@ietf.org>; Tue, 05 Sep 2017 06:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2gnK1cwmFK1qpaHfPLjwhV32CwG0oygbaXt0jhhO2+E=; b=UOkJzMDbbcBsSGQbhitWicqIXVKPq1ZoWXMgz2Dh7+VmP1P2sISOIVvTHLXiUIZUCo M9/hgR7LOwqYgLb0LYdll3BTo/2Wz9un9Age3GuFc0k7gb76JPpRe7/iBuuFy6Ufx02u NsH4J7+rryLscM7xksxzilpUnB9QA6EuEibxupOHet/s97MOhn6zBmD64ofZLA1JpZI7 K7nBgwbAKT3E3fMzyqWeO8It79CeXXNT0jjXxfrA/XI/M0ft6VAxRoU5WifJpZU/xoOg PIQN8o9ujMT/AVRvcYQ8c7AKEIcVeWJCmJ/lM9PTkF48PGGLGevKKy26jvQfQWgiMaM3 CsFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2gnK1cwmFK1qpaHfPLjwhV32CwG0oygbaXt0jhhO2+E=; b=KoSPebLmJpG/rbJq3o258iGiJUj+CYJUY0xEKmHxPpPnOd0/NK1fS1vljABzjqYrVV TiA6x7QZrULFP0AMRg0Y4PrO47c/of8q8ARwUQcWyU4aMMU7PsMpYN3xKI6zowcI8D8P Of3izl6D8uEd4pagtRqnyjTi3C1r2MsqaH8F7S7t/6e/uCx8hPowRxmHI7Q4DV4hgpF+ xeX04XLOFKJgAHnukLwNFoeYrENuKDXnfmDQmdiQSZ8AjKDiI2RkZmosiaI7ZnhGIPWP 6+z/7qPfrpmSpOq/TrRPS/GpuGygW1dv1A72mMvZ+6oR3YpS0PO8qUPGtgI4EyAEO91F tLHA==
X-Gm-Message-State: AHPjjUjteUIEFlpB7pQjGRu2jHv6m3nplIvTrmAdOGFL/joC70HpekdZ kIH/b981jWuq0ldMdYRp8VEsAgq0SMy7
X-Google-Smtp-Source: ADKCNb6bym+f8stJSUYFw6cYOcRCAB9p0jRIjhS8ZtBH+JNQOV23SpgnWzRprIJnrnYoWmv22/4XSNcqdSyW1AsyLj4=
X-Received: by 10.107.1.13 with SMTP id 13mr3840466iob.257.1504619155930; Tue, 05 Sep 2017 06:45:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.8.215 with HTTP; Tue, 5 Sep 2017 06:45:55 -0700 (PDT)
In-Reply-To: <b9a35d8e8ccc2f6e0e2d15b112bd32b8.1504584112@squirrel.mail>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <351E3E93-30AF-4F38-ADE0-178DE402D14F@vpnc.org> <C6EEB652-0EAE-48EE-A0CF-938E0D24862A@dotat.at> <1504563125.29012.4.camel@WittsEnd.com> <20170904224218.D6ED78419425@rock.dv.isc.org> <b9a35d8e8ccc2f6e0e2d15b112bd32b8.1504584112@squirrel.mail>
From: Matthew Pounsett <matt@conundrum.com>
Date: Tue, 5 Sep 2017 09:45:55 -0400
Message-ID: <CAAiTEH__tSf8n04LZt2CLTR1XkUKfXzOgJz9zTgsK_9Ks08qZA@mail.gmail.com>
To: "Walter H." <walter.h@mathemainzel.info>
Cc: Mark Andrews <marka@isc.org>, Tony Finch <dot@dotat.at>, mhw@wittsend.com,  "dnsop@ietf.org" <dnsop@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a113bbbc44fee9605587172cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zIsi6JqJ8gn6bIBIBXA3ldAliMY>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 13:45:58 -0000

--001a113bbbc44fee9605587172cf
Content-Type: text/plain; charset="UTF-8"

On 5 September 2017 at 00:01, Walter H. <walter.h@mathemainzel.info> wrote:

>
> > The keyword above was examples which they clearly were.  Most of
> > 1.0.0.0/8 is in use today despite those examples.  The use of local
> > test were also clearly examples.  The Microsoft page above advocated
> > the use literal use of .local which is very different.
>
> and now in the IPv6 ages the same bug is done again ...
>
> 2001:db8: ...
>
> 2001:db8::/32 is reserved for documentation in RFC 3849.  As 192.0.2.0/24,
198.51.100.0/24, and 203.0.113.0/24 were in RFC 5737.

It's not a bug, it's a feature.

--001a113bbbc44fee9605587172cf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 5 September 2017 at 00:01, Walter H. <span dir=3D"ltr">&lt;<a href=
=3D"mailto:walter.h@mathemainzel.info" target=3D"_blank">walter.h@mathemain=
zel.info</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><span class=3D"gmail-"><br>
&gt; The keyword above was examples which they clearly were.=C2=A0 Most of<=
br>
&gt; <a href=3D"http://1.0.0.0/8" rel=3D"noreferrer" target=3D"_blank">1.0.=
0.0/8</a> is in use today despite those examples.=C2=A0 The use of local<br=
>
&gt; test were also clearly examples.=C2=A0 The Microsoft page above advoca=
ted<br>
&gt; the use literal use of .local which is very different.<br>
<br>
</span>and now in the IPv6 ages the same bug is done again ...<br>
<br>
2001:db8: ...<br><br></blockquote><div>2001:db8::/32 is reserved for docume=
ntation in RFC 3849.=C2=A0 As <a href=3D"http://192.0.2.0/24">192.0.2.0/24<=
/a>, <a href=3D"http://198.51.100.0/24">198.51.100.0/24</a>, and <a href=3D=
"http://203.0.113.0/24">203.0.113.0/24</a> were in RFC 5737.</div><div><br>=
</div><div>It&#39;s not a bug, it&#39;s a feature. =C2=A0</div></div><br></=
div></div>

--001a113bbbc44fee9605587172cf--


From nobody Tue Sep  5 08:32:49 2017
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 827F8132D5B; Tue,  5 Sep 2017 08:32:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-ipr@ietf.org>
To: <draft-tale-dnsop-serve-stale@ietf.org>
Cc: dnsop@ietf.org, ipr-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150462556752.14453.11185500932127183922@ietfa.amsl.com>
Date: Tue, 05 Sep 2017 08:32:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zOfTrRdmBw6aZy2RYU_lrGVFdLY>
Subject: [DNSOP] IPR Disclosure Google Inc.'s Statement about IPR related to draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 15:32:47 -0000

Dear David C Lawrence, Warren Kumari:


An IPR disclosure that pertains to your Internet-Draft entitled "Serving
Stale Data to Improve DNS Resiliency" (draft-tale-dnsop-serve-stale) was
submitted to the IETF Secretariat on  and has been posted on the "IETF Page
of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/3059/). The title of the IPR disclosure is
"Google Inc.'s Statement about IPR related to
draft-tale-dnsop-serve-stale"


Thank you

IETF Secretariat


From nobody Tue Sep  5 12:25:43 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1899132E13 for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 12:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 r9tKIGUcjx5I for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 12:25:41 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40C4F124E15 for <dnsop@ietf.org>; Tue,  5 Sep 2017 12:25:41 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id z67so19610362iof.3 for <dnsop@ietf.org>; Tue, 05 Sep 2017 12:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=7m/15Jb8uFtrgopywIn0TAp8egvhz7bI+T8ogmyqni8=; b=q7Tl32MoXj+QxJ/V0vBHyf1Re4E9PBM43bnXpOlmDIhfhH8/fcSTsfVPSsDW0+2CHp JIF9Ub5YAYDqjzjUSR7E4vOFRWhG5DYLjGGRoLUU8KxpkVx7KcP97BWboIQa3Sm7hO+/ Jc29Zy9GxP+/z7E0b2RElQQGOhzkjzD99ZkXOrhge4D5YWBP/yX8UEo02TYQR9CYJgth deucmR8BOi7elBrW2LANe9w0TFEbE+N/A9UDg2KgTTbN9LaK+WcR6AZaROz8100Ra5xP GR+yrRemaFchHVL3miahiA4q8IZcv+zuYAweKAGJ/ShbDZ8o9HNH1M0+vOnRtg/7S5X4 n7qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7m/15Jb8uFtrgopywIn0TAp8egvhz7bI+T8ogmyqni8=; b=PjJJxyp/GSuMwcJpzG/4Ta3JZ5cwuhcipaeM/iOkMxeRoffLZSXx6wNcATknkRFCMc icFsnr4GTtVtMKC0Jbio0dMLJ25YME+PJmOvXm+kicMH8uKvr/n1jNFT09oMe3xsMRSx JiEt/iuNwHFVBi7UuVlYgPyaFI2lpdOfPMsayuMRF9G6uOTl9gnn6QyI1GjGE6U4qvAg pQIpV0N+50DKDPp+Jxnk6ZCXSdGRmQFfWrE9DwY+9u9/iNhKZ239Dt3KzoTVZBIuIkjV IDmoIQZuF7+oMjTlqg3hIOUbC5nrpWxm1A/3I932nHCQr0KQNKjfVdQbV05b6iwmpPKB 3K5A==
X-Gm-Message-State: AHPjjUh9LZLMpYcWvA26sg8cfi2i+c999YFx437AHL65aw4ivPWIUqmV 1fAYE6ydvhzg3pBYcszpyKTtNe+JbBVG
X-Google-Smtp-Source: ADKCNb70qVIIdE4IpvE3o8mmdcEZchoe3OC60qvQIqTep3hPwnCXHrthgUIH3NeDWEZDitc119uqb+OrDgl08ancapI=
X-Received: by 10.107.10.81 with SMTP id u78mr128118ioi.107.1504639540336; Tue, 05 Sep 2017 12:25:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.196.73 with HTTP; Tue, 5 Sep 2017 12:25:39 -0700 (PDT)
From: tjw ietf <tjw.ietf@gmail.com>
Date: Tue, 5 Sep 2017 15:25:39 -0400
Message-ID: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f89925120eb05587631c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qi2L4HQ6_k87sfKtAXlCjugwLdc>
Subject: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 19:25:43 -0000

--001a113f89925120eb05587631c0
Content-Type: text/plain; charset="UTF-8"

August is over and my self-imposed holiday is over, so it's time to get
busy again. We have this document marked as a candidate for adoption.

This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale

The draft is available here:
https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/

Please review this draft to see if you think it is suitable for adoption by
DNSOP, and comments to the list, clearly stating your view.

Please also indicate if you are willing to contribute text, review, etc.

*If You have already stated your position for or against adoption, we are
counting those so you do not need to repeat yourself. *

This call for adoption ends: 19 September 2017

Thanks,
tim wicinski
DNSOP co-chair

--001a113f89925120eb05587631c0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-family:monospace">August=C2=A0is =
over and my self-imposed holiday is over, so it&#39;s time to get busy agai=
n. We=C2=A0have this document marked as a candidate for adoption. =C2=A0</s=
pan></div><div style=3D"font-size:14px"><br></div><div style=3D"font-size:1=
4px"><span style=3D"font-size:14px;font-family:monospace">This starts a for=
mal Call for Adoption for=C2=A0</span><span style=3D"font-size:14px;font-fa=
mily:monospace">draft-tale-dnsop-serve-stale</span></div><div style=3D"font=
-size:14px"><br></div><div style=3D"font-size:14px"><span style=3D"font-siz=
e:14px;font-family:monospace">The draft is available here:</span></div><div=
 style=3D"font-size:14px"><a href=3D"https://datatracker.ietf.org/doc/draft=
-tale-dnsop-serve-stale/">https://datatracker.ietf.org/doc/draft-tale-dnsop=
-serve-stale/</a></div><div style=3D"font-size:14px"><br></div><div style=
=3D"font-size:14px"><span style=3D"font-size:14px;font-family:monospace">Pl=
ease review this draft to see if you think it is suitable for adoption by D=
NSOP, and comments to the list, clearly stating your view.</span></div><div=
 style=3D"font-size:14px"><br></div><div style=3D"font-size:14px"><span sty=
le=3D"font-size:14px;font-family:monospace">Please also indicate if you are=
 willing to contribute text, review, etc.</span></div><div style=3D"font-si=
ze:14px"><br></div><div style=3D"font-size:14px"><span style=3D"font-size:1=
4px">*If You have already stated your position for or against adoption, we =
are counting those so you do not need to repeat yourself. *</span></div><di=
v style=3D"font-size:14px"><br></div><div style=3D"font-size:14px"><span st=
yle=3D"font-size:14px;font-family:monospace">This call for adoption ends: 1=
9 September 2017</span></div><div style=3D"font-size:14px"><br></div><div s=
tyle=3D"font-size:14px"><span style=3D"font-size:14px;font-family:monospace=
">Thanks,</span></div><div style=3D"font-size:14px"><span style=3D"font-siz=
e:14px;font-family:monospace">tim wicinski</span></div><div style=3D"font-s=
ize:14px"><span style=3D"font-size:14px;font-family:monospace">DNSOP co-cha=
ir</span></div><div style=3D"font-size:14px"></div></div>

--001a113f89925120eb05587631c0--


From nobody Tue Sep  5 22:01:19 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D711C1321E3 for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 22:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.132
X-Spam-Level: 
X-Spam-Status: No, score=-4.132 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ev__lAdA1cK5 for <dnsop@ietfa.amsl.com>; Tue,  5 Sep 2017 22:01:13 -0700 (PDT)
Received: from smtpbgau2.qq.com (smtpbgau2.qq.com [54.206.34.216]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2078132139 for <dnsop@ietf.org>; Tue,  5 Sep 2017 22:01:11 -0700 (PDT)
X-QQ-mid: bizesmtp16t1504674064toh8ha4m
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Wed, 06 Sep 2017 13:01:02 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: 8oHFcAoL8WOsuJCNzIvc+d+LH1UKxxeGZEV96GNy1FS5mFO2F0FEUdKFvF+2k dQGTlh2zb/p2IcuzT9N0GMK2apCgov/NFwC0gSkGh0SJzpHCBAbZw+cgaB6KTRVORqhT6iR RohirAJ1OZNFcsR1OkemIe+4yJ678tDydEtvW8PlFCjumLbv5EJ3/VJnXPnLjCERrEX9SF4 K1EaHx+X+NI/crs1MqVWyFJVcV3Z3lmrFt2XeV7uvmxy/FqwDlohd/mF3sAStZvfRCgkg5M Y11ZZGBnuqWpbfafY0U6f57t/03EuFVbDocC7SaeP2zjiRlrCqcDeKvGUxi40MO22zaLVtG p/mo1ZPiQ4pDnXeY5ecurcDCyUs0w==
X-QQ-GoodBg: 2
From: =?utf-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'tjw ietf'" <tjw.ietf@gmail.com>, "'dnsop'" <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
In-Reply-To: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
Date: Wed, 6 Sep 2017 13:01:05 +0800
Message-ID: <01a101d326cd$2681d370$73857a50$@cn>+E5AE0031AE5A86E9
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A2_01D32710.34A51370"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdMmfMldAycBwQsOTced2hrYtdKVaAATo6ZA
Content-Language: zh-cn
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uX8oEsmoWQ-Rp0Bd8Yx66jJU1zA>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgRE5TT1AgQ2FsbCBmb3IgQWRvcHRpb24g?= =?utf-8?q?-_draft-tale-dnsop-serve-stale?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 05:01:18 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01A2_01D32710.34A51370
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Just quickly go through the draft.=20

=20

One question: Is it worthwhile to let sub-resolver to know that the =
answer is stale. It is true that =E2=80=9Cstale bread is better than no =
bread=E2=80=9D on the recursive server=E2=80=99s point of view. But it =
may be not true for sub-resolver or measurement probes .

=20

The user may want to be more informative. They may have alterative =
recursive servers or other resolution path ( some apps have their own =
resolution path) . I have this thought analogous to buying a sushi in =
7&11 shop. I pay attention to the  =
<http://dict.youdao.com/w/expiration%20time/#keyfrom=3DE2Ctranslation> =
expiration time. I think I need to know it.=20

=20

Davey

=20

=E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:dnsop-bounces@ietf.org] =
=E4=BB=A3=E8=A1=A8 tjw ietf
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B49=E6=9C=886=E6=97=A5 =
3:26
=E6=94=B6=E4=BB=B6=E4=BA=BA: dnsop
=E4=B8=BB=E9=A2=98: [DNSOP] DNSOP Call for Adoption - =
draft-tale-dnsop-serve-stale

=20

August is over and my self-imposed holiday is over, so it's time to get =
busy again. We have this document marked as a candidate for adoption. =20

=20

This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale

=20

The draft is available here:

https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/

=20

Please review this draft to see if you think it is suitable for adoption =
by DNSOP, and comments to the list, clearly stating your view.

=20

Please also indicate if you are willing to contribute text, review, etc.

=20

*If You have already stated your position for or against adoption, we =
are counting those so you do not need to repeat yourself. *

=20

This call for adoption ends: 19 September 2017

=20

Thanks,

tim wicinski

DNSOP co-chair


------=_NextPart_000_01A2_01D32710.34A51370
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Just quickly go through the draft. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>One question: Is it worthwhile to let sub-resolver to know that the =
answer is stale<a name=3D"_MailEndCompose">. It is true that =
=E2=80=9Cstale bread is better than no bread=E2=80=9D on the recursive =
server=E2=80=99s point of view. But it may be not true for sub-resolver =
or measurement probes .<o:p></o:p></a></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The user may want to be more informative. They may have alterative =
recursive servers or other resolution path ( some apps have their own =
resolution path) . I have this thought analogous to buying a sushi in =
7&amp;11 shop. I pay attention to the </span><a =
href=3D"http://dict.youdao.com/w/expiration%20time/#keyfrom=3DE2Ctranslat=
ion"><span lang=3DEN-US =
style=3D'font-family:"Calibri","sans-serif";color:#1F497D;text-decoration=
:none'>expiration time</span></a><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>. I think I need to know it. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Davey<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt'>=E5=8F=91=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt'> DNSOP [mailto:dnsop-bounces@ietf.org] =
</span><b><span style=3D'font-size:10.0pt'>=E4=BB=A3=E8=A1=A8 =
</span></b><span lang=3DEN-US style=3D'font-size:10.0pt'>tjw =
ietf<br></span><b><span =
style=3D'font-size:10.0pt'>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt'> 2017</span><span =
style=3D'font-size:10.0pt'>=E5=B9=B4<span =
lang=3DEN-US>9</span>=E6=9C=88<span lang=3DEN-US>6</span>=E6=97=A5<span =
lang=3DEN-US> 3:26<br></span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> =
dnsop<br></span><b>=E4=B8=BB=E9=A2=98<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> [DNSOP] DNSOP Call for =
Adoption - =
draft-tale-dnsop-serve-stale<o:p></o:p></span></span></p></div></div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-family:"Courier =
New"'>August&nbsp;is over and my self-imposed holiday is over, so it's =
time to get busy again. We&nbsp;have this document marked as a candidate =
for adoption. &nbsp;</span><span =
lang=3DEN-US><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>This starts a =
formal Call for Adoption =
for&nbsp;draft-tale-dnsop-serve-stale</span><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>The draft is =
available here:</span><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'><a =
href=3D"https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/">h=
ttps://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/</a><o:p></o=
:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>Please review this =
draft to see if you think it is suitable for adoption by DNSOP, and =
comments to the list, clearly stating your view.</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>Please also =
indicate if you are willing to contribute text, review, etc.</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'>*If You =
have already stated your position for or against adoption, we are =
counting those so you do not need to repeat yourself. =
*<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>This call for =
adoption ends: 19 September 2017</span><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>Thanks,</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>tim =
wicinski</span><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Courier New"'>DNSOP =
co-chair</span><span lang=3DEN-US =
style=3D'font-size:10.5pt'><o:p></o:p></span></p></div></div></div></div>=
</body></html>
------=_NextPart_000_01A2_01D32710.34A51370--




From nobody Wed Sep  6 04:05:10 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA1E1323A3 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 04:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 JuS5OL75Scgr for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 04:05:07 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 01EC613202D for <dnsop@ietf.org>; Wed,  6 Sep 2017 04:05:07 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:8446:8785:9383:89ad] (unknown [IPv6:2603:3015:3603:8e00:8446:8785:9383:89ad]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 0CB5C5406F9; Wed,  6 Sep 2017 07:05:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.6\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
Date: Wed, 6 Sep 2017 07:04:59 -0400
Cc: dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BB952F9-615B-40BE-9B79-D7882CF2AB8E@puck.nether.net>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
To: tjw ietf <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.1.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hUbZBf9q2qSTdjfJ1ScAqkRiNPA>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 11:05:08 -0000

I support adoption of the document.

- Jared

> On Sep 5, 2017, at 3:25 PM, tjw ietf <tjw.ietf@gmail.com> wrote:
>=20
> August is over and my self-imposed holiday is over, so it's time to =
get busy again. We have this document marked as a candidate for =
adoption. =20
>=20
> This starts a formal Call for Adoption for =
draft-tale-dnsop-serve-stale
>=20
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
>=20
> Please review this draft to see if you think it is suitable for =
adoption by DNSOP, and comments to the list, clearly stating your view.
>=20
> Please also indicate if you are willing to contribute text, review, =
etc.
>=20
> *If You have already stated your position for or against adoption, we =
are counting those so you do not need to repeat yourself. *
>=20
> This call for adoption ends: 19 September 2017
>=20
> Thanks,
> tim wicinski
> DNSOP co-chair
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Wed Sep  6 07:00:21 2017
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E25A133047; Wed,  6 Sep 2017 07:00:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <dnsop@ietf.org>, <draft-west-let-localhost-be-localhost@ietf.org>, <dnsop-chairs@ietf.org>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150470641938.15184.2404701351393125981.idtracker@ietfa.amsl.com>
Date: Wed, 06 Sep 2017 07:00:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aIDtGbdezOsG8JRNo05SYyVP6XU>
Subject: [DNSOP] The DNSOP WG has placed draft-west-let-localhost-be-localhost in state "Call For Adoption By WG Issued"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:00:19 -0000

The DNSOP WG has placed draft-west-let-localhost-be-localhost in state
Call For Adoption By WG Issued (entered by Tim Wicinski)

The document is available at
https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/


From nobody Wed Sep  6 07:03:47 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36567132FE7 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pe6FgRCosy0W for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:03:44 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1619C132FF6 for <dnsop@ietf.org>; Wed,  6 Sep 2017 07:00:03 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id y123so23934619iod.0 for <dnsop@ietf.org>; Wed, 06 Sep 2017 07:00:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=3xVmRp9ek/AvkVjIJc5jbjroNd8FCbYsvxFQrkuRaMQ=; b=LLxSsjET21fC+loab6XzNLTULXYMHyZPrDCWZOWBOmzbF16lwA0DWp/ZrdnanRdlRs 4fjYqXhn/mwNidmO109+BcKfOHtiABXsIAqJUos5F/Y1B+wEJOuzsS3kTh7sMVoEmoRk 0ZYZ3JBRp3cagRjrqJhpcI/EgIyljdFMToUOsTp0b4lGsdwXWVJ+pg2V335k4UOKdAUw qXCYWnyMPXNJxqB14OB5y4X23+umAUNrn3zUok+BqmijBP1TIxg2W1KTt8piPrA3ed8c pj17T0YxmrJrMwTA1KhBQPlXJuoL4rMhBBJG0ViMPrvNJ6FPkZ+u/fgNovFrAAnEvU9s TAZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3xVmRp9ek/AvkVjIJc5jbjroNd8FCbYsvxFQrkuRaMQ=; b=XuUynFdqKK0+FMvbjPJm8y1kJ0JhxukLw7SDkhMkByBzNz+OCrRV9Xts5AAjfrEWwq bUcTQGi3p6/NlIQN44+q+0VgcNrmTmOq1IQsdN+XCdJ9z28Kp1GRCqx+R1yXwraOV3QY Lml9kVC6tLEXHaSbEdTOs1ZrQyPtgysnZ+fKoeDloPLJKrOt8thu9sfD1fqtH6g8hVWo wnhIWNBYM+6oZsZGGDdRxeywHWZS0yZFzRiorKk1iZUNKO8JAEnRlpeiHo+cQBe7+jtb Oyoz5RhCswSfBs5x6KIDmSwr0K3lZhQqA3C/Jg6Pk9/zuLRkrikzwenHbSVDzitMWuNv hpCw==
X-Gm-Message-State: AHPjjUhKF5BAeqnYFv+0KFkakVFLdSE0WQS5j9laH8Q/dgaipmytUC8l fKcH7BqBuEMLpvi3lZEKDT/QWxBWk8tr
X-Google-Smtp-Source: AOwi7QB3hR8bD6C113BH3sxPHeC3z9UFrmf4IcWDFZx9/TJxDcVyeQbWuaHzV8N0cyCHbpvEdb+mfq1USM/8iW6kfLc=
X-Received: by 10.107.1.13 with SMTP id 13mr2706077iob.257.1504706402207; Wed, 06 Sep 2017 07:00:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.196.73 with HTTP; Wed, 6 Sep 2017 07:00:01 -0700 (PDT)
From: tjw ietf <tjw.ietf@gmail.com>
Date: Wed, 6 Sep 2017 10:00:01 -0400
Message-ID: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113bbbc4984f05055885c247"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eGn3kxRhoj1r4c-zHbE1_ozKq_k>
Subject: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:03:46 -0000

--001a113bbbc4984f05055885c247
Content-Type: text/plain; charset="UTF-8"

When the idea of having a Call for Adoption for this document came up, we
thought long and hard about this one.  However, the comments from the
working group focused this document to address the specific issue of the
local hostname.

This starts a formal Call for Adoption for
draft-west-let-localhost-be-localhost

The draft is available here:
https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/

Please review this draft to see if you think it is suitable for adoption by
DNSOP, and comments to the list, clearly stating your view.

Please also indicate if you are willing to contribute text, review, etc.

This call for adoption ends: 20 September 2017

Thanks,
tim wicinski
DNSOP co-chair

--001a113bbbc4984f05055885c247
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-family:monospace">When the idea o=
f having a Call for Adoption for this document came up, we thought long and=
 hard about this one.=C2=A0 However, the comments from the working group fo=
cused this document to address the specific issue of the local=C2=A0hostnam=
e. =C2=A0 =C2=A0=C2=A0</span></div><div style=3D"font-size:14px"><br></div>=
<div style=3D"font-size:14px"><span style=3D"font-size:14px;font-family:mon=
ospace">This starts a formal Call for Adoption for=C2=A0</span><span style=
=3D"font-size:14px;font-family:monospace">draft-west-let-localhost-be-local=
host</span></div><div style=3D"font-size:14px"><br></div><div style=3D"font=
-size:14px"><span style=3D"font-size:14px;font-family:monospace">The draft =
is available here:</span></div><div style=3D"font-size:14px"></div><div sty=
le=3D"font-size:14px"><a href=3D"https://datatracker.ietf.org/doc/draft-wes=
t-let-localhost-be-localhost/" style=3D"color:rgb(0,0,238)">https://datatra=
cker.ietf.org/doc/draft-west-let-localhost-be-localhost/</a></div><div styl=
e=3D"font-size:14px"><br></div><div style=3D"font-size:14px"><span style=3D=
"font-size:14px;font-family:monospace">Please review this draft to see if y=
ou think it is suitable for adoption by DNSOP, and comments to the list, cl=
early stating your view. =C2=A0</span></div><div style=3D"font-size:14px"><=
br></div><div style=3D"font-size:14px"><span style=3D"font-size:14px;font-f=
amily:monospace">Please also indicate if you are willing to contribute text=
, review, etc.</span></div><div style=3D"font-size:14px"><br></div><div sty=
le=3D"font-size:14px"><span style=3D"font-family:monospace">This call for a=
doption ends: 20 September 2017</span></div><div style=3D"font-size:14px"><=
br></div><div style=3D"font-size:14px"><span style=3D"font-size:14px;font-f=
amily:monospace">Thanks,</span></div><div style=3D"font-size:14px"><span st=
yle=3D"font-size:14px;font-family:monospace">tim wicinski</span></div><div =
style=3D"font-size:14px"><span style=3D"font-size:14px;font-family:monospac=
e">DNSOP co-chair</span></div><div style=3D"font-size:14px"></div></div>

--001a113bbbc4984f05055885c247--


From nobody Wed Sep  6 07:29:08 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28098132A8E for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 J5Qfi-9qEXPO for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:29:04 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FBF3132A85 for <dnsop@ietf.org>; Wed,  6 Sep 2017 07:29:04 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id b82so19833420qkc.4 for <dnsop@ietf.org>; Wed, 06 Sep 2017 07:29:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Yz4Ehwd3FPqzJPcZeGDWyzSCRN4V/rucc8s9CIHBdlY=; b=ePvdxhQpvloRPATs1+/RrahrUDhhsnsf0X3HRP1Gn8/8Sx+oEWaWKDNI8PgyH8QeNK b1qa21i61vOAfEyYipOmweEusNXZbmz/1cS7mjHDqkN/DbyBS7pO74iJUA03FJm5rJ7j i0WRwR31PY7grUrRB47mY9cEhlozrbNlvevC1ItxPxdKhIIWW4KHdrkWIHjjvDJRbyti HGn0Y/B2uYRRzd7p0KL8z3mvIsUKPcHylzQ1xQSsbT8hUMXgVwGZED8xgu8v90GJFbFC L6H4LhtDlAE9w0gWPpuIx3g3VsO0A3F+oY239NylbmISTaRZ/AtIph5pUAi4GvnMz/C1 qKhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Yz4Ehwd3FPqzJPcZeGDWyzSCRN4V/rucc8s9CIHBdlY=; b=aaHypECCkAFcACE1SwfLJ//uLkQMULu1IYV7pVl9AM6KesuCrQQWpHAQCE02CEqm2x 80rYw4SlULAp+94Y3BzrvqfoAiS38VgcGS1MDs6dgLWJZxNQ1qNN0Dr/xrsz3M0YhQ27 2pLVAd4b7gx2rfgxvb5YE55wws65Lu3nz6mwEs7Egc4+Zkwa5AEgOgCJq6CsXGrV9aBW kU7O+3beCEGNBO/1oQXs0hQszY3XB+cvHMPHyvWbTl03v24hl+Xm8CVSiSnFwSfJRVZS k8AhjOJhYoXmsKZFYoIN/1zVRENe9H6B5UobKYSSVp/AgCu2MapR4ybvr0xGykOUWpq3 8XyQ==
X-Gm-Message-State: AHPjjUjnyCG5+dzbiGiGPFPz9jyflwExJVYBXmTHKDahPzhqR23EF+OS Wvk4mol8ArR2MIDW
X-Google-Smtp-Source: ADKCNb7LHZfA5HulhEK5bTTvdbYF2xPtQTkA4PqM+oBDMYwjE4rjZkLRwvVoKErIqmjc1cSpnfd/qA==
X-Received: by 10.55.155.6 with SMTP id d6mr3893206qke.55.1504708143597; Wed, 06 Sep 2017 07:29:03 -0700 (PDT)
Received: from cavall.ether.lede.home (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id m93sm2191379qte.72.2017.09.06.07.29.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Sep 2017 07:29:02 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
Date: Wed, 6 Sep 2017 10:29:00 -0400
Cc: dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EAdha6uwolbt7h0Bruzr64Jmou0>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:29:06 -0000

The document as written still waffles between insecure delegation and =
secure denial of existence.   I think that if the document were =
published with the recommendation of an insecure delegation, this would =
be actively harmful.   If it's published with the secure denial of =
existence, it would probably improve the state of the art.

Unfortunately I don't think that calls for adoption really give us a =
basis for stating such preferences.   But that's basically where I land =
on this.   I would be perfectly happy to support this document if it =
does the right thing, but I'm dead set against it if it doesn't.   I am =
of course willing to participate in working on the document if =
adopted=E2=80=94I've already sent some text, and am grateful to the =
author for having for the most part accepted my proposed changes.


From nobody Wed Sep  6 07:33:31 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 734BF132A85 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jSy7j9rUSwZC for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:33:28 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A8E132A8E for <dnsop@ietf.org>; Wed,  6 Sep 2017 07:33:27 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id j141so20117651ioj.4 for <dnsop@ietf.org>; Wed, 06 Sep 2017 07:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lzvlwoVtCdGtgZmmU2Bzb94EF4BfeyWRC9YaWlDliz4=; b=kej3kv35i1pS/FBRO199loDhkdt4uwanQQkE0cg1d69WG26p0a5Ut1tJ7hV216K+2Z Cu51n1P5/Z+0zMEw/hqoFijeYZIoc7X1aq3zk7CMQJJTwpo8/tiLzUOJhSJVBQLBjMx0 MxuQr0k5HkPgLDGioQQwLNLizHhWiOt+dk96Vvph1kaJGVCbFFM61QKvRXw00sOQPJmA DoRpjd41FDdJFQpCxtev3HsluWFXKyWSCrjUhHFLsH2xUdOpHis0/BSjGX0S5ip0BCs3 vLjyDPzICANaKakXR0+mcVTjua9Qi6pLyYhohFe3vT3KAMTxzm6z6Sx8W2Kw8h5WwRG3 8Qww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lzvlwoVtCdGtgZmmU2Bzb94EF4BfeyWRC9YaWlDliz4=; b=T50nyV9fkz8QiAojOJs+0RbdrCvTzV4lgrzjcgmy8/5ADwkdqG/wL9LMotP8N1yFN9 6DFcX5JtDuFcD9VuNk51sSstCgYIwbqZwpL4Nj9LU7/kUL7GyykgILECzAg3nqK0U4oN i7ZiTMoROXnjioOqhh+ULsYXV/9ZnZK4BdlAWi783DshVOfVQPwx1ggEC3o+Ng1JuOXE DthwOe+Dhp1wsrVfN2J3gRJgqqbOGqOE2zdWWfjc1m3Kgf5PilKIytinKB33BYGWHXSf Xhv4XoMjr04HWdrUb8Kjz9vMBgmmjGBdFMKYDmj95njy2eWyI4K75EE7CwJ5BzuAgCqk 7igg==
X-Gm-Message-State: AHPjjUgjhL5h4HABc9k6G5Uq6ABSqAn4i1R5Yx4M/n887rh9C8t+CVxm QZeNLESPwOeGzkTZKeWV8CENzaWMmA==
X-Google-Smtp-Source: AOwi7QD/DYLH725tB/PFRKsSGZmDFUNo4QSm1sGpCTz6V1L8EbXjvvfsfAWMXNLID5Ctfv2nLaf5yRsIX0fhqA+r0KA=
X-Received: by 10.107.1.13 with SMTP id 13mr2840180iob.257.1504708407078; Wed, 06 Sep 2017 07:33:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.196.73 with HTTP; Wed, 6 Sep 2017 07:33:26 -0700 (PDT)
In-Reply-To: <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Wed, 6 Sep 2017 10:33:26 -0400
Message-ID: <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113bbbc41833d70558863a3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/asOot68z3FLDIXpVBlv6q3XaShE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:33:29 -0000

--001a113bbbc41833d70558863a3b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ted

Thanks.  The document still waffles, but it 'waffles less' than it did
initially.  But Mike is committed to working that and any other issue which
may arise.

tim

On Wed, Sep 6, 2017 at 10:29 AM, Ted Lemon <mellon@fugue.com> wrote:

> The document as written still waffles between insecure delegation and
> secure denial of existence.   I think that if the document were published
> with the recommendation of an insecure delegation, this would be actively
> harmful.   If it's published with the secure denial of existence, it woul=
d
> probably improve the state of the art.
>
> Unfortunately I don't think that calls for adoption really give us a basi=
s
> for stating such preferences.   But that's basically where I land on this=
.
>  I would be perfectly happy to support this document if it does the right
> thing, but I'm dead set against it if it doesn't.   I am of course willin=
g
> to participate in working on the document if adopted=E2=80=94I've already=
 sent some
> text, and am grateful to the author for having for the most part accepted
> my proposed changes.
>
>

--001a113bbbc41833d70558863a3b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ted<div><br></div><div>Thanks.=C2=A0 The document still wa=
ffles, but it &#39;waffles less&#39; than it did initially.=C2=A0 But Mike =
is committed to working that and any other issue which may arise.=C2=A0</di=
v><div><br></div><div>tim</div></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Wed, Sep 6, 2017 at 10:29 AM, Ted Lemon <span dir=3D=
"ltr">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugu=
e.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The document =
as written still waffles between insecure delegation and secure denial of e=
xistence.=C2=A0 =C2=A0I think that if the document were published with the =
recommendation of an insecure delegation, this would be actively harmful.=
=C2=A0 =C2=A0If it&#39;s published with the secure denial of existence, it =
would probably improve the state of the art.<br>
<br>
Unfortunately I don&#39;t think that calls for adoption really give us a ba=
sis for stating such preferences.=C2=A0 =C2=A0But that&#39;s basically wher=
e I land on this.=C2=A0 =C2=A0I would be perfectly happy to support this do=
cument if it does the right thing, but I&#39;m dead set against it if it do=
esn&#39;t.=C2=A0 =C2=A0I am of course willing to participate in working on =
the document if adopted=E2=80=94I&#39;ve already sent some text, and am gra=
teful to the author for having for the most part accepted my proposed chang=
es.<br>
<br>
</blockquote></div><br></div>

--001a113bbbc41833d70558863a3b--


From nobody Wed Sep  6 07:35:54 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BED1132FC0 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 m0SmqAco4UJK for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:35:51 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3067B132C2B for <dnsop@ietf.org>; Wed,  6 Sep 2017 07:35:51 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id b23so19907367qkg.1 for <dnsop@ietf.org>; Wed, 06 Sep 2017 07:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=h018JThKRNq/G5VpXYWSLt8FZVlitvX1r2Edx2wcAZw=; b=aKIu05J9XPYc4RTYMs9lKGr53+duxSJ08ueIcUp+zU3xwkOYFtXTckP6uc5mipgP/2 908jZijFSUryFrIKbmydv++FX8ygm8VlWl1FZnJM9iTIoVWucxOSEScaCzCj8vfs4Hj4 UFLtf4dzKkCn47bhHH0DSd8NhOulaRNoob8Xpmr7gG1CZ9wP2MCuIAVmffyxZ3yyC9NS 7lLt3ZJg4THQKwAnPHDut1V8KMyusXHuoMshOX+O4Z8rzFqlvNmAA06kLuiDdtLHtOzV wn+dAGffyyaaF1ERWSG2Wq637AbIp9gC6P/eiiIdm0Lz9lImjICFW6fSugAXK7KN4i85 dI4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=h018JThKRNq/G5VpXYWSLt8FZVlitvX1r2Edx2wcAZw=; b=JChfalb2i5iKBHaT4dSHZrys7FIK4XQphWsKsuZzjAL1JPuP9b+VtypaKRzc2F4l2o n86ALw3dotc+0ry0Byo1wZGYnndkGgRBRUeSrh1/RSVt+jhJEWG3fFFpCxPO2S9zmxw/ 2Y0HWZRFp5hJCHQHDRNfCW0PiX+pvgkpl+PWcngLl84uukQ0vdjdhhr2WWrpkMeTEzuB 7bTmpmUeEDrjPFElVxcKu2ciMFhQFMuT/CABltgHVVOh/uUZWP467oI0sgfmCs+vRLLT 2tuoP2NPM46ConHw3zdOSrbKzqhqs39KeZyC6QntFBPKnxDZsW3HHvHrSXzuoDxy/S6g zc1A==
X-Gm-Message-State: AHPjjUgMhwt0C640+DFJ+1N3Ckhh39/O8KiSXUZcZ7yYlnIrXUEBSbcf FYXiq9oW8uFNtoEfzMI7gw==
X-Google-Smtp-Source: ADKCNb5q7F3UUuIi4+NAqZeG9mB9CHvpbUbT1nu6N1MPDiMplNH0xjzoheYMKg5e+rgnI0F7Ko2hyw==
X-Received: by 10.55.166.73 with SMTP id p70mr3545235qke.342.1504708550250; Wed, 06 Sep 2017 07:35:50 -0700 (PDT)
Received: from cavall.ether.lede.home (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id u64sm2236184qkc.68.2017.09.06.07.35.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Sep 2017 07:35:49 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FB6AD6D3-C9C3-4CD6-BD5D-702226EA7086"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 6 Sep 2017 10:35:47 -0400
In-Reply-To: <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com>
Cc: dnsop <dnsop@ietf.org>
To: Tim Wicinski <tjw.ietf@gmail.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KKcRktXCcRg6lXksFiV-65Dc0MA>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:35:52 -0000

--Apple-Mail=_FB6AD6D3-C9C3-4CD6-BD5D-702226EA7086
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
> Thanks.  The document still waffles, but it 'waffles less' than it did =
initially.  But Mike is committed to working that and any other issue =
which may arise.=20

The question I really have is not whether Mike is willing=E2=80=94he's =
stated that he is.   It's whether the working group is willing, since =
returning NXDOMAIN is an actual change in behavior from the original =
specification in RFC 6761, and will likely result in some breakage, =
since it can safely be assumed that some stacks are currently following =
the RFC6761 advice.




--Apple-Mail=_FB6AD6D3-C9C3-4CD6-BD5D-702226EA7086
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 6, 2017, at 10:33 AM, tjw ietf &lt;<a =
href=3D"mailto:tjw.ietf@gmail.com" class=3D"">tjw.ietf@gmail.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">Thanks.&nbsp; The document still waffles, but it 'waffles =
less' than it did initially.&nbsp; But Mike is committed to working that =
and any other issue which may arise.&nbsp;</div></div></blockquote><br =
class=3D""></div><div>The question I really have is not whether Mike is =
willing=E2=80=94he's stated that he is. &nbsp; It's whether the working =
group is willing, since returning NXDOMAIN is an actual change in =
behavior from the original specification in RFC 6761, and will likely =
result in some breakage, since it can safely be assumed that some stacks =
are currently following the RFC6761 advice.</div><div><br =
class=3D""></div><div><br class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_FB6AD6D3-C9C3-4CD6-BD5D-702226EA7086--


From nobody Wed Sep  6 07:45:34 2017
Return-Path: <rlb@ipv.sx>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632CC13243E for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 k-CqE8TCvA8d for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 07:45:29 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59BA0132A65 for <dnsop@ietf.org>; Wed,  6 Sep 2017 07:45:29 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id k20so5475147wre.4 for <dnsop@ietf.org>; Wed, 06 Sep 2017 07:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MkAL7vSiQnc60jrB1vgncZYbax6HEG8jTr0h4reI5uE=; b=TP8tSUVDgGRp0qi+/sKGTwPLDihfascZ17VWT3F5WUm11I+NYyDjn9jSAn25UM+ALl dwE4mQ13BWF3jiLJrKr3GgwCMB5si8/aGZHOX/yLI13VE/JOlA8fgr1UASKHDpwAKAmh gPva6ayINYdCzygkTuBTd6/g//JyJRFYVTgmBlWiZXX0DUs7WLUuQTV1hW7lpZx/g46J 9sa68v8wp3ItKgyoLDx5BiajPXhSduwiW3tZ3rtDstJyW8VTc+Q4wdb4s7P9yJVaqbIT CBFGeZS+a6/7Id7AKrIS3fJKalrpzRMBtvaFAm7dpHRhW2JQW1NDccvCtWLzWKyR4fHk UKSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MkAL7vSiQnc60jrB1vgncZYbax6HEG8jTr0h4reI5uE=; b=fpKMCthcb0TrkbTXI2kyWgoI/0Ay3J47fq05+xIl1UVkOQ/Ev8vZQ7YwME8Yu2oO2+ Q35hudsZnHo4DVCvi5aiC3Idtk9geTeU0+F5ZO0FndC8D2IImNymUe4B/kcgd9oKH4Gv hf8S52HEkT54e5pMOv+nUoknUO79Evhs7U+FwVYd3rGeXeqRXrfCD/UGzcT93x2QzLiG jwHXLRrJ6df8mbWLiLU+H9WDe0eP1Iml+VhY+sPuhHmTUyXchYIjPSletMzDbXgTboUF +ZsbCVXph8Um0gfJgL6lT+EYV+MYisV3DDd9/4a5ZKgbdMFWd+24UUkAF1H9kgH8oTGl zUzw==
X-Gm-Message-State: AHPjjUgBmc4iqoQrG6ym7UEiPIP+yBkEHl+IFMB4VCVo20j3MxeouOXg DUKrdo1EM6CkPotbrv8NdBl1DRW3DakD
X-Google-Smtp-Source: ADKCNb5XAlLLXLXBYtrQw11M3mginEtG47EN/bpXrrPiruyGQjgxQJB7FSp1F16uXZ9dS/tMqmUk07Fy612iSX7E8yY=
X-Received: by 10.223.175.116 with SMTP id z107mr1694256wrc.210.1504709127634;  Wed, 06 Sep 2017 07:45:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.159.200 with HTTP; Wed, 6 Sep 2017 07:45:27 -0700 (PDT)
In-Reply-To: <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 6 Sep 2017 10:45:27 -0400
Message-ID: <CAL02cgT90FirU+jwiu70EhOZKZ16S9nA7wJ6CeudR5ua0wiTtw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f53a00b1c0a05588665cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0gi8Gm4_Z1s4gv6GL510XZuwgnE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 14:45:32 -0000

--f403045f53a00b1c0a05588665cc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am strongly in support of the WG adopting this draft.  It will allow
applications to deliver a better developer experience and higher security.

As Ted notes, there is a possibility of breakage.  If something on a host
is relying on an external resolver to provide localhost resolution in
accordance with RFC 6761.  However, that behavior is almost certainly not
secure to start with, so this breakage is of the good, "increasing
security" kind.

--Richard

On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
>
> Thanks.  The document still waffles, but it 'waffles less' than it did
> initially.  But Mike is committed to working that and any other issue whi=
ch
> may arise.
>
>
> The question I really have is not whether Mike is willing=E2=80=94he's st=
ated that
> he is.   It's whether the working group is willing, since returning
> NXDOMAIN is an actual change in behavior from the original specification =
in
> RFC 6761, and will likely result in some breakage, since it can safely be
> assumed that some stacks are currently following the RFC6761 advice.
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

--f403045f53a00b1c0a05588665cc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I am strongly in support of the WG adopting this draf=
t.=C2=A0 It will allow applications to deliver a better developer experienc=
e and higher security.</div><div><br></div><div>As Ted notes, there is a po=
ssibility of breakage.=C2=A0 If something on a host is relying on an extern=
al resolver to provide localhost resolution in accordance with RFC 6761.=C2=
=A0 However, that behavior is almost certainly not secure to start with, so=
 this breakage is of the good, &quot;increasing security&quot; kind.</div><=
div><br></div><div>--Richard<br></div></div><div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mell=
on@fugue.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div s=
tyle=3D"word-wrap:break-word"><span class=3D"">On Sep 6, 2017, at 10:33 AM,=
 tjw ietf &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.i=
etf@gmail.com</a>&gt; wrote:<div><blockquote type=3D"cite"><div><div style=
=3D"font-family:Helvetica;font-size:18px;font-style:normal;font-variant-cap=
s:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-ind=
ent:0px;text-transform:none;white-space:normal;word-spacing:0px">Thanks.=C2=
=A0 The document still waffles, but it &#39;waffles less&#39; than it did i=
nitially.=C2=A0 But Mike is committed to working that and any other issue w=
hich may arise.=C2=A0</div></div></blockquote><br></div></span><div>The que=
stion I really have is not whether Mike is willing=E2=80=94he&#39;s stated =
that he is. =C2=A0 It&#39;s whether the working group is willing, since ret=
urning NXDOMAIN is an actual change in behavior from the original specifica=
tion in RFC 6761, and will likely result in some breakage, since it can saf=
ely be assumed that some stacks are currently following the RFC6761 advice.=
</div><div><br></div><div><br></div><br></div><br>_________________________=
_____<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
<br></blockquote></div><br></div>

--f403045f53a00b1c0a05588665cc--


From nobody Wed Sep  6 08:57:53 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409F8132D57 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 08:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 gqcoevH_IVoz for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 08:57:50 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DDD5132D52 for <dnsop@ietf.org>; Wed,  6 Sep 2017 08:57:50 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:58413) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dpcfi-000qvL-2v (Exim 4.89) (return-path <dot@dotat.at>); Wed, 06 Sep 2017 16:57:47 +0100
Date: Wed, 6 Sep 2017 16:55:21 +0100
From: Tony Finch <dot@dotat.at>
To: Ted Lemon <mellon@fugue.com>
cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
In-Reply-To: <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
Message-ID: <alpine.DEB.2.11.1709061625540.2676@grey.csi.cam.ac.uk>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/T8xnYOTTmDJi00SsoJAIOSNVqaE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 15:57:52 -0000

Ted Lemon <mellon@fugue.com> wrote:
>
> It's whether the working group is willing, since returning NXDOMAIN is
> an actual change in behavior from the original specification in RFC
> 6761, and will likely result in some breakage, since it can safely be
> assumed that some stacks are currently following the RFC6761 advice.

I was looking at query traffic recently to prepare for deleting localhost
entries from our main zone
(http://news.uis.cam.ac.uk/articles/2017/09/01/deleting-localhost-entries-from-the-cam-ac-uk-dns-zone)

It was reassuring to see there were very few leaked localhost queries,
whether bare or with the search path appended. So it seems that stub
resolvers are successfully sinking localhost queries as they should.

I have configured the resolvers I run pedantically to include the empty
zones that aren't built-in to BIND, including localhost. So my setup is a
lot more RFC 6761 than the default. (But I'll happily delete most of it
when the cheese shop reaches production.)

Based on the low volume of localhost query traffic and the lack of
RFC 6761 conformance in at least one common recursive server, I think the
change from positive to negative responses will only affect a tiny
number of things that are already buggy.

A related thing that needs to be covered is the reverse DNS for 127.0.0.1
and ::1 - pedants like me have configured PTR records for those addresses,
which become useless when the forward domain goes away (if they aren't
useless already). BIND returns a built-in NXDOMAIN for them by default
which is justified by RFC 5735 though that spec doesn't mention the DNS.

Perhaps let-localhost-be-localhost should explicitly require reverse DNS
behaviour to match the forward DNS, i.e. positive answers generated in
stubs and NXDOMAIN from recursive servers.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Irish Sea: West 4 or 5, decreasing 3 for a time, backing southwest 5 or 6
later. Slight or moderate. Showers later. Good.


From nobody Wed Sep  6 09:05:47 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88178132031 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 09:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 PF9cqze03DX9 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 09:05:44 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0BB6124207 for <dnsop@ietf.org>; Wed,  6 Sep 2017 09:05:44 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 5B65A20C02; Wed,  6 Sep 2017 09:05:44 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Matthijs Mekking <matthijs@pletterpet.nl>
Cc: dnsop@ietf.org
References: <ybl4luqq05v.fsf@w7.hardakers.net> <7d425067-84ff-2471-d39a-0c3a20c0116c@pletterpet.nl>
Date: Wed, 06 Sep 2017 09:05:44 -0700
In-Reply-To: <7d425067-84ff-2471-d39a-0c3a20c0116c@pletterpet.nl> (Matthijs Mekking's message of "Thu, 20 Jul 2017 14:34:56 +0200")
Message-ID: <yblvakvn76v.fsf@w7.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/npAuDmqk1lesq7b5o7QFcSnnKi4>
Subject: Re: [DNSOP] requesting WGLC for 5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 16:05:45 -0000

Matthijs Mekking <matthijs@pletterpet.nl> writes:

Thanks for all your points, and I've gone through and handled them all
in the text (including discussing that we update 7583 per your request).

> 2. waitTime only adds one queryInterval, while Itrp adds two. I believe
> to be safe on the publishing side, two queryIntervals is needed. RFC
> 7583 explains:
>
>    A validator will treat it as a trust anchor the next
>    time it retrieves the RRset, a process that can take up to another
>    queryInterval (the third term).

This is the one that had me think with a whiteboard for a while.  If I
can sum it up differently, the problem is that 30 days may not be a
factor of the queryInterval.  Thus:

    N * queryInterval >= 30

Where N is the number of queries to get somewhere over 30 days.

So Irtp is waiting an extra queryInterval to account for this
possibility.

Mathematically, I think the actually time needed to wait is 30 %
queryInterval, which may actually be 0 in some cases and just shy of
queryInterval in others.  Sound about right?

> 4. Both definitions (Itrp and waitTime) don't really take into
> consideration the retryTime defined in RFC 5011. Perhaps that can be
> used for defining the extra safety margin.

I'll have to add some text about that.  I don't think we can solve the
case for broken networks, though.  But it's an important point to bring up.

-- 
Wes Hardaker
USC/ISI


From nobody Wed Sep  6 10:12:48 2017
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9255713292F for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 GULcx5mpkbSp for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:12:44 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52B9F13292A for <dnsop@ietf.org>; Wed,  6 Sep 2017 10:12:44 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id o42so4575621wrb.3 for <dnsop@ietf.org>; Wed, 06 Sep 2017 10:12:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=V8u4vg7Ka+CRRZlrglA2tg7D3qNNUI/fxbSlTxTzsBc=; b=oGVzmAcFR0TnUpvKgIs3m4fwqGm03rpqZH4gIxNbxDu2ocropee8YZhm36dXwHlJQ5 0bh8x+U6lmgfLqaoVOnRVEg+QqehwH540FRJOih2vEvlMNsnc10RM12w2KNj41tnvafH HZKk/HeMvhIdm/a5brAijlmZ+gnV3PHBp0iYcZh2VMxZ0E7LsEgdN0tF6mUcyGboXW2t pKHzz2BUfyNk9JIubPg94baseVTbzU5YoyacIlXYqZu5DhoVv2xhaaT238o7Zj5807re yfqN2GJD/9nb9Q+NUhdI0k7D526Z8WeSk3JbRdDMZkKb9oRRcqnLKKzZQF512OeROa+Z 8OsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=V8u4vg7Ka+CRRZlrglA2tg7D3qNNUI/fxbSlTxTzsBc=; b=Nu/oK1t284V78CI4R/KyyGnIghhebOPFFAUQRjzDePQxi0MH1MRmeeOIzaKFzdgF4M lIo0qftaILn3MqMtoStnjryyGfmIf2TaL6LvuXYjlJDE6OlAkkLN5zDWrDG3pg9H4AiE FSGL7MMBhvlHBZNVF760Glanlowc1+lMdIBnlOnnb09uXhtsR9ie9di8e3x0x9R/kKjY G+Cx+7NNkjfhwkllCdI7c1zxHUlQzpVkD/93isPI39hXrFJtDvhfj3DaFZE0dt6+wcB4 y/M7E0y3chkZXf+esqmtUebdNIGzTpxgKA+kRy82quwd/Lm8zbIYlDplN1BtBykJfajh 9gkA==
X-Gm-Message-State: AHPjjUjXhhveAXLr/Ynnhf8dRSBrnMeGtYgI8irQ2ZAefSYjGNAwDyDn IbTOdJzrLbPZVVPlNPy0RD6gRYo0Iyoj
X-Google-Smtp-Source: ADKCNb6aZwEIS5pt/QVVG5ASO1ls3dx/8bS9dt5gzErrzEduVH5lwEIE/PNnh+ezImo//yUbEEuvGBUchXlRhjO+xz0=
X-Received: by 10.223.134.168 with SMTP id 37mr2078143wrx.311.1504717962781; Wed, 06 Sep 2017 10:12:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Wed, 6 Sep 2017 10:12:02 -0700 (PDT)
In-Reply-To: <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 6 Sep 2017 13:12:02 -0400
Message-ID: <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lEIIpk45_uIvRAz22EiFHhDGrxo>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 17:12:46 -0000

On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <mellon@fugue.com> wrote:
> On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
>
> Thanks.  The document still waffles, but it 'waffles less' than it did
> initially.  But Mike is committed to working that and any other issue whi=
ch
> may arise.
>
>
> The question I really have is not whether Mike is willing=E2=80=94he's st=
ated that
> he is.   It's whether the working group is willing, since returning NXDOM=
AIN
> is an actual change in behavior from the original specification in RFC 67=
61,
> and will likely result in some breakage, since it can safely be assumed t=
hat
> some stacks are currently following the RFC6761 advice.
>

Actually, I suspect that the breakage will be fairly minimal -- Google
Public DNS appears to have been returning NXDOMAIN since launch:
dig +nocmd +nostats localhost @8.8.8.8
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55075
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;localhost. IN A

;; AUTHORITY SECTION:
. 14208 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017090502
1800 900 604800 86400


and Verisign returns NOERROR (probably also since launch):
dig +nocmd +nostats localhost @64.6.64.6
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44657
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;localhost. IN A

;; ANSWER SECTION:
localhost. 10800 IN A 127.0.0.1


This doesn't seem to have caused any breakage - or, at least, we
haven't heard of any, and apparently basically no-one had noticed a
difference :-)

W
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>



--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Sep  6 10:23:37 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0190B133136 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=Vlc22PgQ; dkim=pass (1024-bit key) header.d=yitter.info header.b=NYey7p4n
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 HM6Xy4_q-yfU for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:23:33 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FDAA133135 for <dnsop@ietf.org>; Wed,  6 Sep 2017 10:23:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 58160BEA1E for <dnsop@ietf.org>; Wed,  6 Sep 2017 17:23:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504718580; bh=onTft6OVAYreakS9Qy1sLzK/czQCAPpeg3lH0Ug/wlM=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Vlc22PgQmUo6Kj7Nsw1stG0KBN8Qf5ZxiAOfM1TK3Tw2v3DeEn1n+1aIzKQZn6fD6 bPh8uJGc0NQRFmgfQKMSyBTdgO4JRwROwGLwXeCGwqimUX7ZRBI9n1bvVzgiAz265S lfgqtNVzAkcpp7xh9LN3BrvDLE7tv+3qrGOD4UBE=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4Q9-k5wU8Eu for <dnsop@ietf.org>; Wed,  6 Sep 2017 17:22:58 +0000 (UTC)
Date: Wed, 6 Sep 2017 13:22:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504718578; bh=onTft6OVAYreakS9Qy1sLzK/czQCAPpeg3lH0Ug/wlM=; h=Date:From:To:Subject:References:In-Reply-To:From; b=NYey7p4nVfTfmJlnZIpS1AdCaqypE/Zf+pLCqYyJe1Wf9VePouVONsXZOOYTZDbdq EVzy3abevCCdFTBLnA1u6LnV6j7t7+q5nuaZagguN49l04YXz9Obn9larC88tdQe9/ lBf9ZtCQBIAw40HEXYfl6buebBLeOVyCMvTIjwg4=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com> <59AB67A2.3000008@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59AB67A2.3000008@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6ApoTdZxQRs1g-tAn859Nb_WUm8>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 17:23:35 -0000

On Sat, Sep 02, 2017 at 07:23:30PM -0700, Paul Vixie wrote:

> it to BIND4. but we have yet to automate it. and this rat hole is a deep
> one, because sometimes the disconnection is "all the links connecting my
> city / state / island / country to the rest of the global internet" and
> sometimes it's just your laptop, or one vm, or your LAN, or your house or
> office or campus.

Nevertheless, I think you're right that this is a part of a much
bigger issue.  I was vaguely hopeful, once, that it was an issue
homenet was going to tackle, but I think it won't.  The issue, really,
is that people want an inter-net that works tolerably well when
arbitrary parts of the infrastructure break, and they want to do that
without any management overhead, and they want to do it on networks
that were designed more as "Internet clients" than "internetworking
networks".

Ironically, of course, the early Internet had a relatively high
failure tolerance, because the network wasn't that reliable yet.  One
of the nice parts of the design of the DNS (no, really, I come to
praise it!) is the way it is distributed in two ways.  The authority
is distributed, so there's not a giant central database administrator
and also so that authoritative servers for important stuff local to
you can be close to you.  But the data is also distributed (via caches
and long TTLs) so that many failure scenarios are hidden from view.
Of course, as a practical matter we have centralised authoritative
servers to an uncomfortable degree (and I'm aware my employer is part
of the reason for that).  Similarly, we have lowered TTLs in order to
get fast changes through the DNS in order to use it as a
systems-management tool.  But the knobs are there.

None of this, however, helps in a network enviroment that is treated
as (or even conceived as) one big client network, with all the "real"
resources in the ISP.  Such networks aren't really part of the
inter-networking environment.  Most home and many small corporate
networks are like this.  As the devices deployed in them get more
sophisticated, they represent a greater threat.  But they also
represent a rich mine of "why can't I just?" questions such as those
that are on display in this thread.

I don't know what to do about that.  There's no Internet driver
license, and yet the desire for an RFC1918 analogue name is to me
clearly something that only makes sense if you come at this from the
"client network" perspective.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Sep  6 10:35:46 2017
Return-Path: <bgreene@senki.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513A9132055 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=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 GDIZ9XHR-UWu for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:35:42 -0700 (PDT)
Received: from smtp69.iad3a.emailsrvr.com (smtp69.iad3a.emailsrvr.com [173.203.187.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD4551321A2 for <dnsop@ietf.org>; Wed,  6 Sep 2017 10:35:42 -0700 (PDT)
Received: from smtp1.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp1.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id E8E8162A6; Wed,  6 Sep 2017 13:35:39 -0400 (EDT)
X-Auth-ID: bgreene@senki.org
Received: by smtp1.relay.iad3a.emailsrvr.com (Authenticated sender: bgreene-AT-senki.org) with ESMTPSA id E8FFC5CD5;  Wed,  6 Sep 2017 13:35:38 -0400 (EDT)
X-Sender-Id: bgreene@senki.org
Received: from [10.0.3.167] (118.red-193-153-67.dynamicip.rima-tde.net [193.153.67.118]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:465 (trex/5.7.12); Wed, 06 Sep 2017 13:35:39 -0400
From: Barry Raveendran Greene <bgreene@senki.org>
Message-Id: <03493A21-D474-4643-A20E-A73C9AB75663@senki.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_59BC4BC7-7F3C-47B1-95EC-F7A58BB1B038"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 6 Sep 2017 19:35:32 +0200
In-Reply-To: <5BB952F9-615B-40BE-9B79-D7882CF2AB8E@puck.nether.net>
Cc: tjw ietf <tjw.ietf@gmail.com>
To: Jared Mauch <jared@puck.nether.net>, dnsop <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <5BB952F9-615B-40BE-9B79-D7882CF2AB8E@puck.nether.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VBBthoF5aSLwHU-18JR22bY-CPs>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 17:35:44 -0000

--Apple-Mail=_59BC4BC7-7F3C-47B1-95EC-F7A58BB1B038
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


+1

> On Sep 6, 2017, at 1:04 PM, Jared Mauch <jared@puck.nether.net> wrote:
>=20
> I support adoption of the document.
>=20
> - Jared
>=20
>> On Sep 5, 2017, at 3:25 PM, tjw ietf <tjw.ietf@gmail.com> wrote:
>>=20
>> August is over and my self-imposed holiday is over, so it's time to =
get busy again. We have this document marked as a candidate for =
adoption.
>>=20
>> This starts a formal Call for Adoption for =
draft-tale-dnsop-serve-stale
>>=20
>> The draft is available here:
>> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
>>=20
>> Please review this draft to see if you think it is suitable for =
adoption by DNSOP, and comments to the list, clearly stating your view.
>>=20
>> Please also indicate if you are willing to contribute text, review, =
etc.
>>=20
>> *If You have already stated your position for or against adoption, we =
are counting those so you do not need to repeat yourself. *
>>=20
>> This call for adoption ends: 19 September 2017
>>=20
>> Thanks,
>> tim wicinski
>> DNSOP co-chair
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--Apple-Mail=_59BC4BC7-7F3C-47B1-95EC-F7A58BB1B038
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJZsDHlAAoJEFVuk3AWv0XznfIH/iUbrvpNr4E8k12f8YD2kXgL
tLijp2S4O4kYKxgk7HiqiJWKOg/Q7sg8gFPcbZx5eTuBngtkHNC3iHDeFh4ktIYY
AjgwS42VtB3YxivcN+zgTEDLN6wytOSNGDhdV0lDLguReBCWV1S8HhdwOlOxhpPe
5Mn0DTVQXPlk1fqnr5+LcJZENCvN6r6hVhxBgKGXHTAsijEsa7k4EhdybBquzkac
jd4KXUEAtTNGN1YvxpV54rPagDcasaTF/17BfrFXp82qqA+vKLxz99RApYl7DrVG
OwfvvQNz9orUdJiw5adBFm9PC3EhUOWw2CNjJ74paJMX1V6nh9BXdacde4zWv0w=
=19jS
-----END PGP SIGNATURE-----

--Apple-Mail=_59BC4BC7-7F3C-47B1-95EC-F7A58BB1B038--


From nobody Wed Sep  6 10:39:49 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D24E11321A2 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 E3v_BPEY8Ckd for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:39:47 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C01E8132055 for <dnsop@ietf.org>; Wed,  6 Sep 2017 10:39:47 -0700 (PDT)
Received: from localhost.localdomain (dhcp-182.access.lah1.vix.su [24.104.150.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id A6DE961FA2; Wed,  6 Sep 2017 17:39:47 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Wed, 06 Sep 2017 10:39:47 -0700
Message-ID: <2669890.oGTe88aNEO@localhost.localdomain>
Organization: Vixie Freehold
User-Agent: KMail/4.13.0.25 (Linux/4.12.9-200.fc25.x86_64; KDE/4.14.30; x86_64; ; )
In-Reply-To: <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59AB67A2.3000008@redbarn.org> <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tgzXVQHCAZgH4QyD6H3aYWjmTZA>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 17:39:49 -0000

On Wednesday, September 06, 2017 01:22:57 PM Andrew Sullivan wrote:
> On Sat, Sep 02, 2017 at 07:23:30PM -0700, Paul Vixie wrote:
> > it to BIND4. but we have yet to automate it. and this rat hole is a deep
> > one, because sometimes the disconnection is "all the links connecting my
> > city / state / island / country to the rest of the global internet" and
> > sometimes it's just your laptop, or one vm, or your LAN, or your house or
> > office or campus.
> 
> ...  Such networks aren't really part of the
> inter-networking environment.  ...

right. but this is why we fail, and can't be used as a reason we won't change.

vixie


From nobody Wed Sep  6 10:49:03 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97411321A2 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=QiL9uSts; dkim=pass (1024-bit key) header.d=yitter.info header.b=josFFDuV
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 kb28vzqdH8Br for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 10:49:01 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC830132055 for <dnsop@ietf.org>; Wed,  6 Sep 2017 10:49:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id F2485BEA1E for <dnsop@ietf.org>; Wed,  6 Sep 2017 17:49:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504720140; bh=zwgh8+IMbOA7/Wc61gQokSC3lFDjAwK5ddxX+eW1/WI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=QiL9uStsTtd2+0U28BbYXukQYXilcA4mfrfzsXeWkdMCPpXcSv8Un0l614dvtdxlA YJ3yND7nvywMXL8u1D8lec1j7VM1uDqq/Nf+IR6WG5TljSPYzBprf3Wf7mIL4+hJAj AxwjULRNlWqku2/meBVq8JkJXfscBgn/tc7G+Ou8=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kz0fTQhLYvX6 for <dnsop@ietf.org>; Wed,  6 Sep 2017 17:48:59 +0000 (UTC)
Date: Wed, 6 Sep 2017 13:48:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1504720139; bh=zwgh8+IMbOA7/Wc61gQokSC3lFDjAwK5ddxX+eW1/WI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=josFFDuVG3LyUCYhutCz/PQgyOE+UAs1qgKPgD0/Sne3DB0drG0TzjoXvYveUAmdS 2aGRGA6XfsvlF/w/ou9nQ+gpqct17vVSl8xRkkT/HA12CpCnPPx3OtGDIimp4fh8yV MFYUh5Nel5zpTA6NrMiC6mQpkRgZ7wOg9iZ9otYk=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170906174858.g57mmohlxcpdjyjj@mx4.yitter.info>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59AB67A2.3000008@redbarn.org> <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info> <2669890.oGTe88aNEO@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2669890.oGTe88aNEO@localhost.localdomain>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RnV1Bdg7ViaFfPxoa8SbY1_-m1s>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 17:49:03 -0000

On Wed, Sep 06, 2017 at 10:39:47AM -0700, Paul Vixie wrote:
> right. but this is why we fail, and can't be used as a reason we won't change.

Oh, yes, we are in complete agreement there.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Sep  6 11:03:56 2017
Return-Path: <jsha@eff.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6D91329E3 for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 11:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 Un90jazOwuty for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 11:03:53 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4376132055 for <dnsop@ietf.org>; Wed,  6 Sep 2017 11:03:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2;  h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=DeSKq2X70a+unFvPcrdnBjC0kh4tDZ4cxW3VVOzYRKI=;  b=ExzqUQw6LD59VKotO1KHWwbBDQsfoVcEsOWyjmNB6tvmpy2i7BVz/psHwhIgL5gMJ98Ch+RchWtG7pZ5SEFN4OTVmcwUQkNJOiozEZEStDGFS4UHQzj4fis6aiI/NYt5Fot2xsVb7WIrEaW7Qa0dvc0xAWzA9KFK5lT2Z+5S1eg=;
Received: ; Wed, 06 Sep 2017 11:03:49 -0700
To: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <ae542849-b208-a06f-d9fc-38a17ae0a0c3@eff.org>
Date: Wed, 6 Sep 2017 11:03:51 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------9464A44862E80ADAD489DDA4"
Content-Language: en-US
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xsqv0L0HseboZwBvuG2j8XgrpdM>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 18:03:55 -0000

This is a multi-part message in MIME format.
--------------9464A44862E80ADAD489DDA4
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

I support adopting this draft.

On 09/06/2017 07:00 AM, tjw ietf wrote:
> When the idea of having a Call for Adoption for this document came up,
> we thought long and hard about this one.  However, the comments from
> the working group focused this document to address the specific issue
> of the local hostname.     
>
> This starts a formal Call for Adoption
> for draft-west-let-localhost-be-localhost
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/
>
> Please review this draft to see if you think it is suitable for
> adoption by DNSOP, and comments to the list, clearly stating your view.  
>
> Please also indicate if you are willing to contribute text, review, etc.
>
> This call for adoption ends: 20 September 2017
>
> Thanks,
> tim wicinski
> DNSOP co-chair
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--------------9464A44862E80ADAD489DDA4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I support adopting this draft.<br>
    <br>
    <div class="moz-cite-prefix">On 09/06/2017 07:00 AM, tjw ietf wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com">
      <div dir="ltr">
        <div><span style="font-family:monospace">When the idea of having
            a Call for Adoption for this document came up, we thought
            long and hard about this one.  However, the comments from
            the working group focused this document to address the
            specific issue of the local hostname.     </span></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">This starts a
            formal Call for Adoption for </span><span
            style="font-size:14px;font-family:monospace">draft-west-let-localhost-be-localhost</span></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">The draft is
            available here:</span></div>
        <div style="font-size:14px"><a
href="https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/"
            style="color:rgb(0,0,238)" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/</a></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">Please review
            this draft to see if you think it is suitable for adoption
            by DNSOP, and comments to the list, clearly stating your
            view.  </span></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">Please also
            indicate if you are willing to contribute text, review, etc.</span></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span style="font-family:monospace">This
            call for adoption ends: 20 September 2017</span></div>
        <div style="font-size:14px"><br>
        </div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">Thanks,</span></div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">tim wicinski</span></div>
        <div style="font-size:14px"><span
            style="font-size:14px;font-family:monospace">DNSOP co-chair</span></div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
DNSOP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DNSOP@ietf.org">DNSOP@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dnsop">https://www.ietf.org/mailman/listinfo/dnsop</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------9464A44862E80ADAD489DDA4--


From nobody Wed Sep  6 11:48:17 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB0F13294B for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 11:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 CvzGrxoyKYHM for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 11:48:14 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33F211321A2 for <dnsop@ietf.org>; Wed,  6 Sep 2017 11:48:14 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:35076) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dpfMw-000N0Q-39 (Exim 4.89) (return-path <dot@dotat.at>); Wed, 06 Sep 2017 19:48:11 +0100
Date: Wed, 6 Sep 2017 19:48:10 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Vixie <paul@redbarn.org>
cc: dnsop@ietf.org
In-Reply-To: <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
Message-ID: <alpine.DEB.2.11.1709061900240.2628@grey.csi.cam.ac.uk>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com> <59AB67A2.3000008@redbarn.org> <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/42Hj7T1H28dOSl4fP-Jcyv8F8oE>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 18:48:16 -0000

Paul Vixie <paul@redbarn.org> wrote:
>
> we do not have well defined automation for making local names work when
> the internet connection is down. at a very modest level of necessary and
> inevitable complexity, one's own in-perimeter recursive servers can't
> find one's own in-perimeter authority servers. so if your internet
> connection goes down, then way more stuff becomes effectively
> unreachable than what's on the far side of the disconnection point.
>
> mark andrews faced disconnections of this kind as a daily part of his
> work about 30 years ago when he developed the "stub zone" feature and
> contributed it to BIND4. but we have yet to automate it.

This won't address the deeper problems that you outlined, but...

It occurs to me that this could be made a lot simpler with the right
flavour of metazone / catalogue zone.

On our site we encourage those running BIND to secondary our local zones,
but it's horrible to configure and there's a lot of manualarity to
co-ordinate delegation changes. But it has nice resilience and performance
properties.

However I'm doubtful that it's worth trying to make it possible to
automatically discover a catalogue zone for the local domains on the local
network...

Forwarding to our recursive servers is a lot simpler to configure and has
easier support for DNSSEC validation. Sadly DNSSEC reintroduces the
external dependency problem, but serve-stale should mitigate that when
our recursive servers support it.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Biscay: Westerly or northwesterly 3 or 4, occasionally 5 in north. Moderate,
occasionally rough in north. Mainly fair. Good.


From nobody Wed Sep  6 21:17:18 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15DB6132D7E for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 uWrqYfFjM0-T for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:17:14 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DBAC1321A3 for <dnsop@ietf.org>; Wed,  6 Sep 2017 21:17:14 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id A2C0024AE1F; Thu,  7 Sep 2017 04:16:57 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5F51C160043; Thu,  7 Sep 2017 04:17:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4298C160071; Thu,  7 Sep 2017 04:17:04 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KkMQP3cIkafF; Thu,  7 Sep 2017 04:17:04 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id B2D03160043; Thu,  7 Sep 2017 04:17:03 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id ED0BB8482BFF; Thu,  7 Sep 2017 14:16:59 +1000 (AEST)
To: Warren Kumari <warren@kumari.net>
Cc: Ted Lemon <mellon@fugue.com>, Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com>
In-reply-to: Your message of "Wed, 06 Sep 2017 13:12:02 -0400." <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com>
Date: Thu, 07 Sep 2017 14:16:59 +1000
Message-Id: <20170907041659.ED0BB8482BFF@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/75ylxotpMYvBmipXlhI1vDEuBg4>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 04:17:17 -0000

In message <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com>
, Warren Kumari writes:

> On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <mellon@fugue.com> wrote:
> > On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
> >
> > Thanks.  The document still waffles, but it 'waffles less' than it did
> > initially.  But Mike is committed to working that and any other issue
> which
> > may arise.
> >
> >
> > The question I really have is not whether Mike is willinghe's stated
> that
> > he is.   It's whether the working group is willing, since returning
> NXDOMAIN
> > is an actual change in behavior from the original specification in RFC
> 6761,
> > and will likely result in some breakage, since it can safely be assumed
> that
> > some stacks are currently following the RFC6761 advice.
> >
>
> Actually, I suspect that the breakage will be fairly minimal -- Google
> Public DNS appears to have been returning NXDOMAIN since launch:
> dig +nocmd +nostats localhost @8.8.8.8
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55075
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;localhost. IN A
>
> ;; AUTHORITY SECTION:
> . 14208 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017090502
> 1800 900 604800 86400

Which shows absolutely nothing.  

Is 'localhost.' assigned for use by my local machine?  I believe
the answer to that is: Yes.  If if is assigned for use then with
DNSSEC there MUST be a delegation in the root or is this working
group going to overstep its mandate and tell me how I can use the
name localhost.  ICANN stuffed up by not adding the delegation when
the root zone was signed.  It was necessary then and it is still
necessary now.

If we want to create a alternative name and give it much more
restrictive properties than the current assignment of localhost has
then I'm fine with that.  It is actually the correct fix for the
problem statement.  Fiddling with the properties of localhost after
it has been in use for decades isn't the way to address this issue.

Mark

> and Verisign returns NOERROR (probably also since launch):
> dig +nocmd +nostats localhost @64.6.64.6
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44657
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;localhost. IN A
>
> ;; ANSWER SECTION:
> localhost. 10800 IN A 127.0.0.1
>
>
> This doesn't seem to have caused any breakage - or, at least, we
> haven't heard of any, and apparently basically no-one had noticed a
> difference :-)
>
> W
> >
> >
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
> >
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Sep  6 21:42:15 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1714132D7F for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 nbz74g3_0Efq for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:42:10 -0700 (PDT)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2725132392 for <dnsop@ietf.org>; Wed,  6 Sep 2017 21:42:10 -0700 (PDT)
Received: by mail-pg0-x232.google.com with SMTP id m9so19034737pgd.3 for <dnsop@ietf.org>; Wed, 06 Sep 2017 21:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WO4qGygdHveuWAzGj8j6e6ndZ+XuTCFFOYHrGpKOWcg=; b=GehLhGKyM8e79AFPlBWHVY72nR/mm8r9MrJm/eJBndMq48GM9qSletIWfR3YIooELD w4XriBJrhrVwuIeVLhA5RJkGq/Io5X+9vIWQhu+S4HGnhaCshFR+cFcRFVcPHow3ig3g Y3v0pehPS8Z8IXbKsQuCADL/zOZNOcGfgx9AGYyuWfRIHEoYnRVnEs0uhcf+XVNjbocw 9jTdP4ZlUtbZrhtttVoAz/nYbgvPpsb7r34oiCpjvLhf6rK6/SAhpvB2CBufL4iGyXGk YucaHNqQL/zwQRXsccXnHAxUhDDA01s2QWln/rvX0A/fZLWZtr2Dx/IKWAIXxFkUsPPc lirw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WO4qGygdHveuWAzGj8j6e6ndZ+XuTCFFOYHrGpKOWcg=; b=RTh/BYNb76JayHsCU0mvUSW+tevI8RFLA6PeqXsAN8bEP2dQBxxueAqo7B5Ya9ztdr yd3nYxQFL0tAMcCQaYd6lhksIGb7VjyJG6jMD324nJ5fQAwa11BKZu8plX3sSi39W/hP Jz9IrNUImoBfsCxxS1PusdpBaEl1FTxrsPaqcbteLfFLDMJJxBRtHWmfI/Ok7m+RSAYM i6/gY1IKRs8kvNaoPJw4iRksvlMOEBrPVmNG1JeT01eI1LX7E6D7ZKCAAmRmkJx7m3Rv jMVGHgCDViUgd5dVrNvNqPOSjrLx+3yuEEC+8Mw7REvSPlNFLVsL4HhrLJ4R8gPUErOx Yslw==
X-Gm-Message-State: AHPjjUiskzduWDfHoJYMO3IhBTWvjYxF7jr6nRPmlVSDaFcQwKNqHzm9 aScyEPSDQn0MTmzkZkFhYnIBxflg5zwK
X-Google-Smtp-Source: ADKCNb793mdQZ8Nl1jP+zoN536NWQDVVvpWNMVbVLRLD9ipL9/qb48dwq4iIJ/uk9ccnsdPEkU6uzqCBfa6kKBEZdfs=
X-Received: by 10.99.190.77 with SMTP id g13mr1447130pgo.433.1504759330432; Wed, 06 Sep 2017 21:42:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.152.98 with HTTP; Wed, 6 Sep 2017 21:42:09 -0700 (PDT)
Received: by 10.100.152.98 with HTTP; Wed, 6 Sep 2017 21:42:09 -0700 (PDT)
In-Reply-To: <20170907041659.ED0BB8482BFF@rock.dv.isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Sep 2017 00:42:09 -0400
Message-ID: <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Warren Kumari <warren@kumari.net>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="089e0826f99c5cfff90558921502"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ev6p2SA0o4ziqZmNSyS1ZOYq9-o>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 04:42:14 -0000

--089e0826f99c5cfff90558921502
Content-Type: text/plain; charset="UTF-8"

Mark, I really don't think this is a human rights issue. Is there something
that will break for you if the secure denial of existence is left in place?

On Sep 7, 2017 12:17 AM, "Mark Andrews" <marka@isc.org> wrote:

>
> In message <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=
> UQ@mail.gmail.com>
> , Warren Kumari writes:
>
> > On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <mellon@fugue.com> wrote:
> > > On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
> > >
> > > Thanks.  The document still waffles, but it 'waffles less' than it did
> > > initially.  But Mike is committed to working that and any other issue
> > which
> > > may arise.
> > >
> > >
> > > The question I really have is not whether Mike is willinghe's stated
> > that
> > > he is.   It's whether the working group is willing, since returning
> > NXDOMAIN
> > > is an actual change in behavior from the original specification in RFC
> > 6761,
> > > and will likely result in some breakage, since it can safely be assumed
> > that
> > > some stacks are currently following the RFC6761 advice.
> > >
> >
> > Actually, I suspect that the breakage will be fairly minimal -- Google
> > Public DNS appears to have been returning NXDOMAIN since launch:
> > dig +nocmd +nostats localhost @8.8.8.8
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55075
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> >
> > ;; QUESTION SECTION:
> > ;localhost. IN A
> >
> > ;; AUTHORITY SECTION:
> > . 14208 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017090502
> > 1800 900 604800 86400
>
> Which shows absolutely nothing.
>
> Is 'localhost.' assigned for use by my local machine?  I believe
> the answer to that is: Yes.  If if is assigned for use then with
> DNSSEC there MUST be a delegation in the root or is this working
> group going to overstep its mandate and tell me how I can use the
> name localhost.  ICANN stuffed up by not adding the delegation when
> the root zone was signed.  It was necessary then and it is still
> necessary now.
>
> If we want to create a alternative name and give it much more
> restrictive properties than the current assignment of localhost has
> then I'm fine with that.  It is actually the correct fix for the
> problem statement.  Fiddling with the properties of localhost after
> it has been in use for decades isn't the way to address this issue.
>
> Mark
>
> > and Verisign returns NOERROR (probably also since launch):
> > dig +nocmd +nostats localhost @64.6.64.6
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44657
> > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> >
> > ;; QUESTION SECTION:
> > ;localhost. IN A
> >
> > ;; ANSWER SECTION:
> > localhost. 10800 IN A 127.0.0.1
> >
> >
> > This doesn't seem to have caused any breakage - or, at least, we
> > haven't heard of any, and apparently basically no-one had noticed a
> > difference :-)
> >
> > W
> > >
> > >
> > >
> > > _______________________________________________
> > > DNSOP mailing list
> > > DNSOP@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dnsop
> > >
> >
> >
> >
> > --
> > I don't think the execution is relevant when it was obviously a bad
> > idea in the first place.
> > This is like putting rabid weasels in your pants, and later expressing
> > regret at having chosen those particular rabid weasels and that pair
> > of pants.
> >    ---maf
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

--089e0826f99c5cfff90558921502
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Mark, I really don&#39;t think this is a human rights iss=
ue. Is there something that will break for you if the secure denial of exis=
tence is left in place?</div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Sep 7, 2017 12:17 AM, &quot;Mark Andrews&quot; &lt;<a href=
=3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br type=3D"attributi=
on"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
In message &lt;CAHw9_<wbr>iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=3D<wbr>rjpcQ=3Dh5qd=
B7=3D<a href=3D"mailto:UQ@mail.gmail.com">UQ@mail.gmail.com</a><wbr>&gt;<br=
>
, Warren Kumari writes:<br>
<br>
&gt; On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon &lt;<a href=3D"mailto:mello=
n@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt; &gt; On Sep 6, 2017, at 10:33 AM, tjw ietf &lt;<a href=3D"mailto:tjw.i=
etf@gmail.com">tjw.ietf@gmail.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Thanks.=C2=A0 The document still waffles, but it &#39;waffles les=
s&#39; than it did<br>
&gt; &gt; initially.=C2=A0 But Mike is committed to working that and any ot=
her issue<br>
&gt; which<br>
&gt; &gt; may arise.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The question I really have is not whether Mike is willinghe&#39;s=
 stated<br>
&gt; that<br>
&gt; &gt; he is.=C2=A0 =C2=A0It&#39;s whether the working group is willing,=
 since returning<br>
&gt; NXDOMAIN<br>
&gt; &gt; is an actual change in behavior from the original specification i=
n RFC<br>
&gt; 6761,<br>
&gt; &gt; and will likely result in some breakage, since it can safely be a=
ssumed<br>
&gt; that<br>
&gt; &gt; some stacks are currently following the RFC6761 advice.<br>
&gt; &gt;<br>
&gt;<br>
&gt; Actually, I suspect that the breakage will be fairly minimal -- Google=
<br>
&gt; Public DNS appears to have been returning NXDOMAIN since launch:<br>
&gt; dig +nocmd +nostats localhost @<a href=3D"http://8.8.8.8" rel=3D"noref=
errer" target=3D"_blank">8.8.8.8</a><br>
&gt; ;; Got answer:<br>
&gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NXDOMAIN, id: 55075=
<br>
&gt; ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0<b=
r>
&gt;<br>
&gt; ;; QUESTION SECTION:<br>
&gt; ;localhost. IN A<br>
&gt;<br>
&gt; ;; AUTHORITY SECTION:<br>
&gt; . 14208 IN SOA <a href=3D"http://a.root-servers.net" rel=3D"noreferrer=
" target=3D"_blank">a.root-servers.net</a>. <a href=3D"http://nstld.verisig=
n-grs.com" rel=3D"noreferrer" target=3D"_blank">nstld.verisign-grs.com</a>.=
 <a href=3D"tel:2017090502" value=3D"+12017090502">2017090502</a><br>
&gt; 1800 900 604800 86400<br>
<br>
Which shows absolutely nothing.<br>
<br>
Is &#39;localhost.&#39; assigned for use by my local machine?=C2=A0 I belie=
ve<br>
the answer to that is: Yes.=C2=A0 If if is assigned for use then with<br>
DNSSEC there MUST be a delegation in the root or is this working<br>
group going to overstep its mandate and tell me how I can use the<br>
name localhost.=C2=A0 ICANN stuffed up by not adding the delegation when<br=
>
the root zone was signed.=C2=A0 It was necessary then and it is still<br>
necessary now.<br>
<br>
If we want to create a alternative name and give it much more<br>
restrictive properties than the current assignment of localhost has<br>
then I&#39;m fine with that.=C2=A0 It is actually the correct fix for the<b=
r>
problem statement.=C2=A0 Fiddling with the properties of localhost after<br=
>
it has been in use for decades isn&#39;t the way to address this issue.<br>
<br>
Mark<br>
<br>
&gt; and Verisign returns NOERROR (probably also since launch):<br>
&gt; dig +nocmd +nostats localhost @<a href=3D"http://64.6.64.6" rel=3D"nor=
eferrer" target=3D"_blank">64.6.64.6</a><br>
&gt; ;; Got answer:<br>
&gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 44657<=
br>
&gt; ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: =
0<br>
&gt;<br>
&gt; ;; QUESTION SECTION:<br>
&gt; ;localhost. IN A<br>
&gt;<br>
&gt; ;; ANSWER SECTION:<br>
&gt; localhost. 10800 IN A 127.0.0.1<br>
&gt;<br>
&gt;<br>
&gt; This doesn&#39;t seem to have caused any breakage - or, at least, we<b=
r>
&gt; haven&#39;t heard of any, and apparently basically no-one had noticed =
a<br>
&gt; difference :-)<br>
&gt;<br>
&gt; W<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; ______________________________<wbr>_________________<br>
&gt; &gt; DNSOP mailing list<br>
&gt; &gt; <a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnso=
p</a><br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; I don&#39;t think the execution is relevant when it was obviously a ba=
d<br>
&gt; idea in the first place.<br>
&gt; This is like putting rabid weasels in your pants, and later expressing=
<br>
&gt; regret at having chosen those particular rabid weasels and that pair<b=
r>
&gt; of pants.<br>
&gt;=C2=A0 =C2=A0 ---maf<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; DNSOP mailing list<br>
&gt; <a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a>=
<br>
<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</blockquote></div></div>

--089e0826f99c5cfff90558921502--


From nobody Wed Sep  6 21:59:48 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469C31321DC for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 QSQXmH_byBJY for <dnsop@ietfa.amsl.com>; Wed,  6 Sep 2017 21:59:43 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F9CF1321C7 for <dnsop@ietf.org>; Wed,  6 Sep 2017 21:59:43 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 9B75F24AE3D; Thu,  7 Sep 2017 04:59:30 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5C12D160043; Thu,  7 Sep 2017 04:59:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 431A2160071; Thu,  7 Sep 2017 04:59:37 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jskDaQQIxeUM; Thu,  7 Sep 2017 04:59:37 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 97253160043; Thu,  7 Sep 2017 04:59:36 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C194B848328B; Thu,  7 Sep 2017 14:59:34 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com>
In-reply-to: Your message of "Thu, 07 Sep 2017 00:42:09 -0400." <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com>
Date: Thu, 07 Sep 2017 14:59:34 +1000
Message-Id: <20170907045934.C194B848328B@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YqosmSEo_s3-ubBwzScpa8ohNt0>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 04:59:46 -0000

In message <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com>
, Ted Lemon writes:
> 
> Mark, I really don't think this is a human rights issue. Is there something
> that will break for you if the secure denial of existence is left in place?

I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
tools.  Lookups should "just work" like they did before the root
zone was signed.

Mark

> On Sep 7, 2017 12:17 AM, "Mark Andrews" <marka@isc.org> wrote:
> 
> >
> > In message <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=
> > UQ@mail.gmail.com>
> > , Warren Kumari writes:
> >
> > > On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon <mellon@fugue.com> wrote:
> > > > On Sep 6, 2017, at 10:33 AM, tjw ietf <tjw.ietf@gmail.com> wrote:
> > > >
> > > > Thanks.  The document still waffles, but it 'waffles less' than it did
> > > > initially.  But Mike is committed to working that and any other issue
> > > which
> > > > may arise.
> > > >
> > > >
> > > > The question I really have is not whether Mike is willinghe's stated
> > > that
> > > > he is.   It's whether the working group is willing, since returning
> > > NXDOMAIN
> > > > is an actual change in behavior from the original specification in RFC
> > > 6761,
> > > > and will likely result in some breakage, since it can safely be assumed
> > > that
> > > > some stacks are currently following the RFC6761 advice.
> > > >
> > >
> > > Actually, I suspect that the breakage will be fairly minimal -- Google
> > > Public DNS appears to have been returning NXDOMAIN since launch:
> > > dig +nocmd +nostats localhost @8.8.8.8
> > > ;; Got answer:
> > > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55075
> > > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> > >
> > > ;; QUESTION SECTION:
> > > ;localhost. IN A
> > >
> > > ;; AUTHORITY SECTION:
> > > . 14208 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017090502
> > > 1800 900 604800 86400
> >
> > Which shows absolutely nothing.
> >
> > Is 'localhost.' assigned for use by my local machine?  I believe
> > the answer to that is: Yes.  If if is assigned for use then with
> > DNSSEC there MUST be a delegation in the root or is this working
> > group going to overstep its mandate and tell me how I can use the
> > name localhost.  ICANN stuffed up by not adding the delegation when
> > the root zone was signed.  It was necessary then and it is still
> > necessary now.
> >
> > If we want to create a alternative name and give it much more
> > restrictive properties than the current assignment of localhost has
> > then I'm fine with that.  It is actually the correct fix for the
> > problem statement.  Fiddling with the properties of localhost after
> > it has been in use for decades isn't the way to address this issue.
> >
> > Mark
> >
> > > and Verisign returns NOERROR (probably also since launch):
> > > dig +nocmd +nostats localhost @64.6.64.6
> > > ;; Got answer:
> > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44657
> > > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> > >
> > > ;; QUESTION SECTION:
> > > ;localhost. IN A
> > >
> > > ;; ANSWER SECTION:
> > > localhost. 10800 IN A 127.0.0.1
> > >
> > >
> > > This doesn't seem to have caused any breakage - or, at least, we
> > > haven't heard of any, and apparently basically no-one had noticed a
> > > difference :-)
> > >
> > > W
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > DNSOP mailing list
> > > > DNSOP@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/dnsop
> > > >
> > >
> > >
> > >
> > > --
> > > I don't think the execution is relevant when it was obviously a bad
> > > idea in the first place.
> > > This is like putting rabid weasels in your pants, and later expressing
> > > regret at having chosen those particular rabid weasels and that pair
> > > of pants.
> > >    ---maf
> > >
> > > _______________________________________________
> > > DNSOP mailing list
> > > DNSOP@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dnsop
> >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
> 
> --089e0826f99c5cfff90558921502
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"auto">Mark, I really don&#39;t think this is a human rights iss=
> ue. Is there something that will break for you if the secure denial of exis=
> tence is left in place?</div><div class=3D"gmail_extra"><br><div class=3D"g=
> mail_quote">On Sep 7, 2017 12:17 AM, &quot;Mark Andrews&quot; &lt;<a href=
> =3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br type=3D"attributi=
> on"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
> t:1px #ccc solid;padding-left:1ex"><br>
> In message &lt;CAHw9_<wbr>iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=3D<wbr>rjpcQ=3Dh5qd=
> B7=3D<a href=3D"mailto:UQ@mail.gmail.com">UQ@mail.gmail.com</a><wbr>&gt;<br=
> >
> , Warren Kumari writes:<br>
> <br>
> &gt; On Wed, Sep 6, 2017 at 10:35 AM, Ted Lemon &lt;<a href=3D"mailto:mello=
> n@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
> &gt; &gt; On Sep 6, 2017, at 10:33 AM, tjw ietf &lt;<a href=3D"mailto:tjw.i=
> etf@gmail.com">tjw.ietf@gmail.com</a>&gt; wrote:<br>
> &gt; &gt;<br>
> &gt; &gt; Thanks.=C2=A0 The document still waffles, but it &#39;waffles les=
> s&#39; than it did<br>
> &gt; &gt; initially.=C2=A0 But Mike is committed to working that and any ot=
> her issue<br>
> &gt; which<br>
> &gt; &gt; may arise.<br>
> &gt; &gt;<br>
> &gt; &gt;<br>
> &gt; &gt; The question I really have is not whether Mike is willinghe&#39;s=
>  stated<br>
> &gt; that<br>
> &gt; &gt; he is.=C2=A0 =C2=A0It&#39;s whether the working group is willing,=
>  since returning<br>
> &gt; NXDOMAIN<br>
> &gt; &gt; is an actual change in behavior from the original specification i=
> n RFC<br>
> &gt; 6761,<br>
> &gt; &gt; and will likely result in some breakage, since it can safely be a=
> ssumed<br>
> &gt; that<br>
> &gt; &gt; some stacks are currently following the RFC6761 advice.<br>
> &gt; &gt;<br>
> &gt;<br>
> &gt; Actually, I suspect that the breakage will be fairly minimal -- Google=
> <br>
> &gt; Public DNS appears to have been returning NXDOMAIN since launch:<br>
> &gt; dig +nocmd +nostats localhost @<a href=3D"http://8.8.8.8" rel=3D"noref=
> errer" target=3D"_blank">8.8.8.8</a><br>
> &gt; ;; Got answer:<br>
> &gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NXDOMAIN, id: 55075=
> <br>
> &gt; ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0<b=
> r>
> &gt;<br>
> &gt; ;; QUESTION SECTION:<br>
> &gt; ;localhost. IN A<br>
> &gt;<br>
> &gt; ;; AUTHORITY SECTION:<br>
> &gt; . 14208 IN SOA <a href=3D"http://a.root-servers.net" rel=3D"noreferrer=
> " target=3D"_blank">a.root-servers.net</a>. <a href=3D"http://nstld.verisig=
> n-grs.com" rel=3D"noreferrer" target=3D"_blank">nstld.verisign-grs.com</a>.=
>  <a href=3D"tel:2017090502" value=3D"+12017090502">2017090502</a><br>
> &gt; 1800 900 604800 86400<br>
> <br>
> Which shows absolutely nothing.<br>
> <br>
> Is &#39;localhost.&#39; assigned for use by my local machine?=C2=A0 I belie=
> ve<br>
> the answer to that is: Yes.=C2=A0 If if is assigned for use then with<br>
> DNSSEC there MUST be a delegation in the root or is this working<br>
> group going to overstep its mandate and tell me how I can use the<br>
> name localhost.=C2=A0 ICANN stuffed up by not adding the delegation when<br=
> >
> the root zone was signed.=C2=A0 It was necessary then and it is still<br>
> necessary now.<br>
> <br>
> If we want to create a alternative name and give it much more<br>
> restrictive properties than the current assignment of localhost has<br>
> then I&#39;m fine with that.=C2=A0 It is actually the correct fix for the<b=
> r>
> problem statement.=C2=A0 Fiddling with the properties of localhost after<br=
> >
> it has been in use for decades isn&#39;t the way to address this issue.<br>
> <br>
> Mark<br>
> <br>
> &gt; and Verisign returns NOERROR (probably also since launch):<br>
> &gt; dig +nocmd +nostats localhost @<a href=3D"http://64.6.64.6" rel=3D"nor=
> eferrer" target=3D"_blank">64.6.64.6</a><br>
> &gt; ;; Got answer:<br>
> &gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 44657<=
> br>
> &gt; ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: =
> 0<br>
> &gt;<br>
> &gt; ;; QUESTION SECTION:<br>
> &gt; ;localhost. IN A<br>
> &gt;<br>
> &gt; ;; ANSWER SECTION:<br>
> &gt; localhost. 10800 IN A 127.0.0.1<br>
> &gt;<br>
> &gt;<br>
> &gt; This doesn&#39;t seem to have caused any breakage - or, at least, we<b=
> r>
> &gt; haven&#39;t heard of any, and apparently basically no-one had noticed =
> a<br>
> &gt; difference :-)<br>
> &gt;<br>
> &gt; W<br>
> &gt; &gt;<br>
> &gt; &gt;<br>
> &gt; &gt;<br>
> &gt; &gt; ______________________________<wbr>_________________<br>
> &gt; &gt; DNSOP mailing list<br>
> &gt; &gt; <a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
> &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"no=
> referrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnso=
> p</a><br>
> &gt; &gt;<br>
> &gt;<br>
> &gt;<br>
> &gt;<br>
> &gt; --<br>
> &gt; I don&#39;t think the execution is relevant when it was obviously a ba=
> d<br>
> &gt; idea in the first place.<br>
> &gt; This is like putting rabid weasels in your pants, and later expressing=
> <br>
> &gt; regret at having chosen those particular rabid weasels and that pair<b=
> r>
> &gt; of pants.<br>
> &gt;=C2=A0 =C2=A0 ---maf<br>
> &gt;<br>
> &gt; ______________________________<wbr>_________________<br>
> &gt; DNSOP mailing list<br>
> &gt; <a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
> &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"norefer=
> rer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a>=
> <br>
> <br>
> --<br>
> Mark Andrews, ISC<br>
> 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
> PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
>  9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
> =A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
> </blockquote></div></div>
> 
> --089e0826f99c5cfff90558921502--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep  7 05:14:46 2017
Return-Path: <vladimir.cunat@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD2B132D62 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 05:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 upC8LPJV-gxu for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 05:14:44 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA05E1326FE for <dnsop@ietf.org>; Thu,  7 Sep 2017 05:14:43 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:d8cd:12ff:fe4f:872c] (unknown [IPv6:2001:1488:fffe:6:d8cd:12ff:fe4f:872c]) by mail.nic.cz (Postfix) with ESMTPSA id 4533960B80 for <dnsop@ietf.org>; Thu,  7 Sep 2017 14:14:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1504786482; bh=/sTxNv8ARvZv36kf2IFeCRsSBM/6CAik+c7fkNYbUuI=; h=To:From:Date; b=WrbSoV1qZy9Z0sXipwnFrAxn5mLa0pANVrxaRKd0Yj8zMiJQCvVT5PYiuQGFRpaIn 5IkeBc0nYKbNiX89vBiGpZuyBLhWGgCrX+OIp7J6V5sZ5ljvd7yhTVV8NtFJFKfThv S1HpDucl5iC3u0BK3P1IWk7dFlXJioBi/1G/3Dy0=
To: dnsop@ietf.org
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?= <vladimir.cunat+ietf@nic.cz>
Message-ID: <2acc3d1b-7f7f-c74e-e77a-007d48b3cfb0@nic.cz>
Date: Thu, 7 Sep 2017 14:14:42 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cqF6lIfe_11dCqlsQW9P3gTulW8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 12:14:45 -0000

On 09/05/2017 09:25 PM, tjw ietf wrote:
> This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale
I do support the adoption.  We plan to support some kind of
stale-serving in knot-resolver soon, so
I'm certainly willing to review and perhaps contribute some suggestions.

Still, I wonder about the intended level of vagueness of the text.  Is
it meant that the final RFC will leave (larger) unspecified corners?

One issue I see is the case when servers for some zone don't respond but
they (are expected to) only provide a *lead* to the final answer, e.g. a
delegation or a CNAME elsewhere.  In that case it seems useless to wait
without
action until the client timer fires, because we (typically) need at
least one more round-trip to get the final answer.  It might be also
good to touch the issue of negative caching of non-responsivity for some
short time (rfc2308.7.2) and consequently serving stale records
*immediately*.  There's a tradeoff between stale-ness and many resolvers
legitimately hammering servers that are/were under attack (or simply
broken).

I personally think that the length of stale-serving should derive from
the original TTL in some way, as very short TTL suggests the value is
more likely to change and operator doesn't mind increased traffic.
(Raised at IETF99, I think.)  The security section should perhaps stress
that the technique may effectively extend the range of validity in
RRSIGs, as served by validating resolvers (unless I misunderstand the
draft).  I suppose the AD flag might get zeroed in that case, but that
seems not to make much difference in practice (and we *do* want the
stale records, right?)

--Vladimir



From nobody Thu Sep  7 06:23:35 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89404132EE3 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 06:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 ibo4XIGI8xRY for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 06:23:32 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0D57124B18 for <dnsop@ietf.org>; Thu,  7 Sep 2017 06:23:31 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id r141so26827379qke.2 for <dnsop@ietf.org>; Thu, 07 Sep 2017 06:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=sg2GPA0ZFiwys7YcCl3qEf5265W0PRgfZ3eYAAutOeM=; b=Vh7DLE0sDyuiu0Lrzh5bVirGtmOdhyXfpCQCerY31kqKPpf1CbrWuoSEtX+wGECzyZ hM+it+0gaVJz9tX7xyNld5oV687WFgoqGudy2pW6Ep5Whi6ozCE1yK1c00rF86DAv6uB CL0IMNQJljO33ytpMrcTUf2T67ek6nESE0DO3usQFS5EK385KcBd2FmcHaFFNyjSBvet knyMIR6nhssvlXj1qbIYXbPbPjxE/Ud+63wrYqz/jur9SZynxuLd+KpO7kbG7uOZ1s+s JG2TRVW7NVxwGs2EnGuMRe7RlzkAwV+PofrfCtYIc4x1ES/iSZVCDYZ+SK3Usx1Gw8C0 A7Mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=sg2GPA0ZFiwys7YcCl3qEf5265W0PRgfZ3eYAAutOeM=; b=jP7t9CT7jMSWe9AgIX1Rl9nY9DM5imY6ORG9KVLjoxrZkbrobuQcxzBbb0bhWIEU5z wAYpJl7Jiok+9oEXhBqGWJiLsW1FwhqfqMS3v42fAIGGV8VZwqgNHLmXr+TghbcOwcg+ eKxXxXjWf8bEHz99VP8rcPu97jo9MNUjAMLyjTvNmfsd52Ul9efCJKYy9ejH+A4LFiwy 7uFB4whPQ9XZ8FV8CMbLg9aV0kq10LEVTU/ocjXsrgxkhg6eZHZbjQZxuck8mgzqCplT a3vjsmKlyck3UR8wPumjZx2YXEJarWxTk2gBzEDWCAp9eOVF7lf0qo77zxGI/OnY270s QVtw==
X-Gm-Message-State: AHPjjUgqmAELQ19ewAEzqcZnF8SmVqQDElLJKgUor0t0fTERPMHeKh5X E0dp8UVQCyJhmTaR
X-Google-Smtp-Source: ADKCNb6Pl0Mv/nvB6vHeVmEoigDUJAROTcfwsjmAwIQSD0f639FNG7zSNmUSEE+jNIy9yCxjJfC4KA==
X-Received: by 10.55.59.136 with SMTP id i130mr3313201qka.99.1504790611085; Thu, 07 Sep 2017 06:23:31 -0700 (PDT)
Received: from cavall.ether.lede.home (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id k21sm1625478qke.79.2017.09.07.06.23.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Sep 2017 06:23:30 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A45069B7-3CEB-4059-B7C6-83242C40F42A"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 7 Sep 2017 09:23:29 -0400
In-Reply-To: <20170907045934.C194B848328B@rock.dv.isc.org>
Cc: Warren Kumari <warren@kumari.net>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
To: Mark Andrews <marka@isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qK-mSXrCXR2qtL7v9vt4vHrIfBc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 13:23:33 -0000

--Apple-Mail=_A45069B7-3CEB-4059-B7C6-83242C40F42A
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
> I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
> tools.  Lookups should "just work" like they did before the root
> zone was signed.

Because...?


--Apple-Mail=_A45069B7-3CEB-4059-B7C6-83242C40F42A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 7, 2017, at 12:59 AM, Mark Andrews &lt;<a =
href=3D"mailto:marka@isc.org" class=3D"">marka@isc.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">I shouldn't BE =
FORCED to hard code special LOCALHOST rules into DNS</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">tools. &nbsp;Lookups should "just work" like =
they did before the root</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">zone was =
signed.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Because...?</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_A45069B7-3CEB-4059-B7C6-83242C40F42A--


From nobody Thu Sep  7 07:32:45 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF5C3132F1B for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 u_4dGSEAiZqf for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:32:41 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B41BA124B18 for <dnsop@ietf.org>; Thu,  7 Sep 2017 07:32:41 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9062A2806B8 for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:32:39 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 8B5AF2806BE; Thu,  7 Sep 2017 16:32:39 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 84ABD2806B8 for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:32:39 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 82289606D942 for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:32:39 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 7A7B641E1F; Thu,  7 Sep 2017 16:32:39 +0200 (CEST)
Date: Thu, 7 Sep 2017 16:32:39 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20170907143239.x4out34m7weaah2u@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.004096, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.7.142116
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3ITGN6-u75gGCPhvlkCZxcw4-L0>
Subject: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 14:32:45 -0000

draft-wkumari-dnsop-internal-00 proposes to reserve .internal for
RFC1918-like domain names. There is clearly a strong demand for that.
(There is also a strong demand for happy sex, great food, excellent
wines and diamong rings, but let's ignore it for the moment).

The document clearly documents that it will not happen, since it
requires an entire new process at ICANN.

The draft requires a delegation to AS112. Since one of the goals is to
limit leaks, I'm not sure it is a good idea. During the development
of draft-bortzmeyer-dname-root, several people noticed that, unlike
the root, the AS 112 is managed by an unbounded set of unknown
operators. Not great for privacy.

Regarding section 4 (DNSSEC), I wonder if it would be a better idea to
have a name like that in the root:

shouldnotarriveattheroot.internal. IN TXT "Check your resolvers"

This way, requests for anything.internal which leaked at the root
would receive an insecure denial of existence (since there is no DS
for .internal). Problem solved, no?

% dig @localhost -p 9053 NS printer.internal                  
...
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53323
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1
...
;; AUTHORITY SECTION:
intel.			86400 IN NSEC shouldnotarriveattheroot.internal. NS DS RRSIG NSEC
intel.			86400 IN RRSIG NSEC 13 1 86400 (
				20171005142909 20170907142909 6172 .
				RMtu2iXqWAO7LOuB2L/IgbfSuf3h6d7eTQdnEshw+uZT
				WDz0HuSHUeC5YJTxPc2qwGN8xa6dmeGGLX6rTkpWaQ== )
.			86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. (
				2017090702 ; serial
				1800       ; refresh (30 minutes)
				900        ; retry (15 minutes)
				604800     ; expire (1 week)
				86400      ; minimum (1 day)
				)
...

[Note it would not solve the ICANN problem.]

Also, it may be a good idea to add an "Internationalization
considerations" section. If people want a memorable domain name (and
not, say, the TLD .693268ed5948276cb48c3f3339ac465d, which would work
as well), it's because it is typable and rememberable), they may want
it in other languages.




From nobody Thu Sep  7 07:48:11 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0595132F2D for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 1qPIb-Zshby7 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:48:08 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3E6132968 for <dnsop@ietf.org>; Thu,  7 Sep 2017 07:48:08 -0700 (PDT)
Received: from [10.32.60.125] (50-1-98-42.dsl.dynamic.fusionbroadband.com [50.1.98.42]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v87El1GB000137 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Sep 2017 07:47:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-42.dsl.dynamic.fusionbroadband.com [50.1.98.42] claimed to be [10.32.60.125]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
Cc: dnsop@ietf.org
Date: Thu, 07 Sep 2017 07:48:08 -0700
Message-ID: <BE766C50-5FFF-45FE-A551-46CE1F530E9B@vpnc.org>
In-Reply-To: <20170907143239.x4out34m7weaah2u@nic.fr>
References: <20170907143239.x4out34m7weaah2u@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7y9PJywgXl82G8VTLBNwHjhpGu4>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 14:48:10 -0000

On 7 Sep 2017, at 7:32, Stephane Bortzmeyer wrote:

> The document clearly documents that it will not happen, since it
> requires an entire new process at ICANN.

That is a non sequitur. ICANN regularly creates new processes at the 
request of its communities.

--Paul Hoffman, not speaking for ICANN, but speaking as someone who has 
seen ICANN do this for over a decade


From nobody Thu Sep  7 07:53:36 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C17132F36 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5jZ2EmQrG8y7 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 07:53:34 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06A8F124B18 for <dnsop@ietf.org>; Thu,  7 Sep 2017 07:53:34 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 8EFE12806BC for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:53:32 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 89B192806BF; Thu,  7 Sep 2017 16:53:32 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 8346E2806BC for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:53:32 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 80A9D60286A3 for <dnsop@ietf.org>; Thu,  7 Sep 2017 16:53:32 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 7A24541E1F; Thu,  7 Sep 2017 16:53:32 +0200 (CEST)
Date: Thu, 7 Sep 2017 16:53:32 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20170907145332.ufbjeg2barlk2nmg@nic.fr>
References: <20170907143239.x4out34m7weaah2u@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170907143239.x4out34m7weaah2u@nic.fr>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.7.144215
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Fr1Q0FmQERqDsHe9XFhD3FeOdnI>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 14:53:35 -0000

On Thu, Sep 07, 2017 at 04:32:39PM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 57 lines which said:

> draft-wkumari-dnsop-internal-00 proposes to reserve .internal for
> RFC1918-like domain names.

And I forgot to say that it could be a good idea to add a reference to
draft-lewis-user-assigned-tlds, for an alternative solution.


From nobody Thu Sep  7 08:21:25 2017
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E708132F94 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 WmxajbBsN3E3 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:21:20 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F98F132F90 for <dnsop@ietf.org>; Thu,  7 Sep 2017 08:21:13 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xp40k39MPzFTB; Thu,  7 Sep 2017 17:21:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504797670; bh=nwZx2iIoGBRl6PnRXVwFsUEpMgvCCueWf6r9I6lseKU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=RMWJf6iz4i2DQ8N96CTTCYZ8FOq1TrlY6NEhfnbgS8kf0LSYpTW3RzO14wkV7oQtU gTPDzI8hqfQ87LaqIKVOC8W07dEWj0q7nuiDicCdOh9bQUv34Xu2/zIFPihdtENdbB lnqxwnY05vM+mOIzjJFmuXiAPWst2ujUKrj6QgJ4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id VDBXocM1AHDq; Thu,  7 Sep 2017 17:21:09 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu,  7 Sep 2017 17:21:09 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 3F1A34EF55; Thu,  7 Sep 2017 11:21:08 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 3F1A34EF55
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 2B2A540B828E; Thu,  7 Sep 2017 11:21:08 -0400 (EDT)
Date: Thu, 7 Sep 2017 11:21:07 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
cc: dnsop@ietf.org
In-Reply-To: <20170907143239.x4out34m7weaah2u@nic.fr>
Message-ID: <alpine.LRH.2.21.1709071119530.21117@bofh.nohats.ca>
References: <20170907143239.x4out34m7weaah2u@nic.fr>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7QvWmY0GRWGMVS5p5KdCCNYq_hk>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 15:21:24 -0000

On Thu, 7 Sep 2017, Stephane Bortzmeyer wrote:

> This way, requests for anything.internal which leaked at the root
> would receive an insecure denial of existence (since there is no DS
> for .internal). Problem solved, no?

Wouldn't that be a secure denial of existence?

AFAIK, the root isn't using NSEC3/optout :)

Paul


From nobody Thu Sep  7 08:31:40 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53796132F80 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 3nmSTH3Jnu2L for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:31:37 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A312132F4B for <dnsop@ietf.org>; Thu,  7 Sep 2017 08:31:37 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D3A1D2806B8; Thu,  7 Sep 2017 17:31:34 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id CE01F2806BF; Thu,  7 Sep 2017 17:31:34 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id C72992806BC; Thu,  7 Sep 2017 17:31:34 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C21F060286A3; Thu,  7 Sep 2017 17:31:34 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id BB04341E1F; Thu,  7 Sep 2017 17:31:34 +0200 (CEST)
Date: Thu, 7 Sep 2017 17:31:34 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Wouters <paul@nohats.ca>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop@ietf.org
Message-ID: <20170907153134.ah3jwwbhfpfftmxb@nic.fr>
References: <20170907143239.x4out34m7weaah2u@nic.fr> <alpine.LRH.2.21.1709071119530.21117@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.21.1709071119530.21117@bofh.nohats.ca>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000450, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.7.151216
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Z-klEXJFOSnPUVufjH38oLtbs2Y>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 15:31:38 -0000

On Thu, Sep 07, 2017 at 11:21:07AM -0400,
 Paul Wouters <paul@nohats.ca> wrote 
 a message of 11 lines which said:

> > This way, requests for anything.internal which leaked at the root
> > would receive an insecure denial of existence (since there is no
> > DS for .internal). Problem solved, no?
> 
> Wouldn't that be a secure denial of existence?

Yes, sorry.

[It may create funny interactions with RFC 8198 but I suspect that
resolvers that leak .internal queries won't implement RFC 8198 anyway.]


From nobody Thu Sep  7 08:42:39 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A110D132D0C for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 nOyIXxhI9BP4 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 08:42:36 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4834D132CE8 for <dnsop@ietf.org>; Thu,  7 Sep 2017 08:42:36 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D01172801B2; Thu,  7 Sep 2017 17:42:34 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id CA9472806BD; Thu,  7 Sep 2017 17:42:34 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id C41C92801B2; Thu,  7 Sep 2017 17:42:34 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C14C5606D942; Thu,  7 Sep 2017 17:42:34 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id B58F741E1F; Thu,  7 Sep 2017 17:42:34 +0200 (CEST)
Date: Thu, 7 Sep 2017 17:42:34 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: tjw ietf <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <20170907154234.3z2zbju2sciiy7wr@nic.fr>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.7.152716
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RO0Lv5DG-fB04wGzaDkgzeLn-JE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 15:42:38 -0000

On Tue, Sep 05, 2017 at 03:25:39PM -0400,
 tjw ietf <tjw.ietf@gmail.com> wrote 
 a message of 77 lines which said:

> This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale
> 
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/

I'm not enthousiastic. We should focus on making the DNS
infrastructure more reliable, not on adding something to a pile of
already fragile protocols.

There is also an opportunity that it masks failures and prevents
people from properly assigning blame: "example.com works if I use
Something Public DNS but not if I use my ISP's resolver, therefore my
ISP is broken".

Also, the current draft does not make crystal-clear that stale data
MUST NOT be served unless no authoritative name server replies.

If it is adopted, I think that requesting some way to convey the fact
it is stale to the client (Davey Song's message) is necessary.

Regarding the draft, I'm surprised by the paragraph starting with
"Paul Vixie has suggested", paragraph which seems to completely ignore
RFC 8020.


From nobody Thu Sep  7 09:21:21 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F37E9132D55 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 09:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 uEPUBSpX9-wt for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 09:21:14 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEFF7124B18 for <dnsop@ietf.org>; Thu,  7 Sep 2017 09:21:14 -0700 (PDT)
Received: from [172.20.16.172] (unknown [50.233.106.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 4A90561FA2; Thu,  7 Sep 2017 16:21:14 +0000 (UTC)
Message-ID: <59B171F8.1050808@redbarn.org>
Date: Thu, 07 Sep 2017 09:21:12 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr>
In-Reply-To: <20170907154234.3z2zbju2sciiy7wr@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/02Amw6T3zE55Z-m0jf6okF1AI9Q>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 16:21:16 -0000

Stephane Bortzmeyer wrote:
> On Tue, Sep 05, 2017 at 03:25:39PM -0400,
>   tjw ietf<tjw.ietf@gmail.com>  wrote
>   a message of 77 lines which said:
>
>> This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale
>>
>> The draft is available here:
>> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
>
> I'm not enthousiastic. We should focus on making the DNS
> infrastructure more reliable, not on adding something to a pile of
> already fragile protocols.

+1.

-- 
P Vixie


From nobody Thu Sep  7 10:36:54 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65FE4132F32 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 10:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 QS8hB8c8G--f for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 10:36:52 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AFAE1204DA for <dnsop@ietf.org>; Thu,  7 Sep 2017 10:36:52 -0700 (PDT)
Received: from localhost (50-1-20-198.dsl.static.fusionbroadband.com [50.1.20.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 9B0CB2215E; Thu,  7 Sep 2017 10:36:50 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: tjw ietf <tjw.ietf@gmail.com>,  dnsop <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr>
Date: Thu, 07 Sep 2017 10:36:50 -0700
In-Reply-To: <20170907154234.3z2zbju2sciiy7wr@nic.fr> (Stephane Bortzmeyer's message of "Thu, 7 Sep 2017 17:42:34 +0200")
Message-ID: <ybltw0emmvh.fsf@wu.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JRouHKKCnGnuk6_fhOoTjQBmvCA>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 17:36:53 -0000

Stephane Bortzmeyer <bortzmeyer@nic.fr> writes:

> I'm not enthousiastic. We should focus on making the DNS
> infrastructure more reliable, not on adding something to a pile of
> already fragile protocols.

I don't believe we have any ideas how to make infrastructure more
reliable in the face of DDoS attacks.  Is your opinion then that
everyone should be using a DDoS resilient cloud provider in case they
ever get attacked?

-- 
Wes Hardaker
USC/ISI


From nobody Thu Sep  7 11:25:22 2017
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8FA132940 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 NIEGfFYEvemx for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:25:19 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26CFF126DD9 for <dnsop@ietf.org>; Thu,  7 Sep 2017 11:25:19 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id g142so477861ita.0 for <dnsop@ietf.org>; Thu, 07 Sep 2017 11:25:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HU0flquxzgqt6EAeWexBd/35igOeylkJq12cxgy5s4g=; b=iM6v8R7iTQxRd4RcIta0BRxyP1noclnmb1yM4fKs7FjGlDWcLuhllMf6Yu+8+rw/GE lAk7SUuR6uyeEK5BV36iipfNGzSuzqVaDsPcyNleKyGeFyCSDma/Z0kWN3oxaeyzlO0m ZVzF7hAzlLmaqTi0U5kQ+ToYJ6qHsAVgOKr90=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HU0flquxzgqt6EAeWexBd/35igOeylkJq12cxgy5s4g=; b=bZEC9xdSm5hyi38qUQe0Ek25vIwd2dur0We+qVXHnSZbxtDi28+MjclyQk0YyGvonM SYWSAZ0lwdVEqCn68r6QRrlotJkdgNVp4DdgoYNzj+YZffG1gWco5a+EVSd6YYckUdWi q0J5YU307M61v4O6GO6EtVV8Op0IEmLUM/HdGY7KU5z0GEzcGhoB5JOzxvFj4O0J5lD3 w/ds/s6di53OjvqkeMxf9USGp4amD7F2EvKRghY58Ienn1u1GGe6NVA7F10gG779Rgai utx8RJwAleg2kH2NYpdNtLVO2PVIO8rIfr+GQzUte7zG/AjEFNB/owZ/4NLXR6LUP9ql cbqg==
X-Gm-Message-State: AHPjjUhz5Jz8BtCE7ByukgbffdpyjCDitJVESPRKiTysRcCxtKLnvIuh SiOTkrdOd1UqWp8yyTOwAQ==
X-Google-Smtp-Source: AOwi7QBrRcSMIqPXPo0cDdP0KZt4KJwrbEQhPifM5B36sImX5wq+3Aisa3UcjwrbJqrFx0AEFauZfw==
X-Received: by 10.36.90.205 with SMTP id v196mr234189ita.70.1504808718383; Thu, 07 Sep 2017 11:25:18 -0700 (PDT)
Received: from node-131fecztrog11ezb2m.ipv6.teksavvy.com (node-131fecztrog11ezb2m.ipv6.teksavvy.com. [2607:f2c0:101:202:34a6:4c4f:7331:a4ce]) by smtp.gmail.com with ESMTPSA id 85sm128495iom.77.2017.09.07.11.25.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Sep 2017 11:25:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20170907154234.3z2zbju2sciiy7wr@nic.fr>
Date: Thu, 7 Sep 2017 14:25:14 -0400
Cc: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Q2LeXXZtm-yhfZa9zrO-4KEvY_U>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 18:25:21 -0000

On 7 Sep 2017, at 11:42, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> On Tue, Sep 05, 2017 at 03:25:39PM -0400,
> tjw ietf <tjw.ietf@gmail.com> wrote=20
> a message of 77 lines which said:
>=20
>> This starts a formal Call for Adoption for =
draft-tale-dnsop-serve-stale
>>=20
>> The draft is available here:
>> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
>=20
> I'm not enthousiastic. We should focus on making the DNS
> infrastructure more reliable, not on adding something to a pile of
> already fragile protocols.

I hear that. I don't have a strong opinion about whether serving stale =
data in general is desirable or abhorrent. However, the pragmatist in me =
says that people are already implementing things like this anyway, and a =
standard approach is better for all concerned than a fragmented set of =
uncomfortably-different implementations, which will surely make =
troubleshooting problems harder.

I also think if a standard specification can be obtained it ought to =
include appropriate instrumentation to allow a response to indicate =
whether data is stale or not. This seems to me just one example of a set =
of additional components we might expect the working group to come up =
with, which in my mind is a good reason to make it a working group =
document.

I support adoption with all of that in mind.


Joe


From nobody Thu Sep  7 11:28:39 2017
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3550A132940 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 PeCxkw4kP9ns for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:28:36 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA13126DD9 for <dnsop@ietf.org>; Thu,  7 Sep 2017 11:28:36 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xp88y36nMzFSp; Thu,  7 Sep 2017 20:28:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504808914; bh=VZ/j+Zcd2lwv0eJtsMs8wUoLtUg7yBUmdtTjkHuoUaA=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=dck4P/V7J8rTVyOc0MnyXzPB02NgZPAaDTTwe/unNQu5XfLWwa+zxyW1ORU+t9yvy Blw9YMqaIUkam1ZrDRboHiEtKDydvs4D/8KnclN6epJsa4LMVb94wLVuNFMEHs2V+i zbX2WfuBrs6aKwpdRL2FC7fyA3iF3GbGdNHGoY0I=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id XlIA0PILk6UB; Thu,  7 Sep 2017 20:28:33 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu,  7 Sep 2017 20:28:32 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id D64754EF55; Thu,  7 Sep 2017 14:28:31 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D64754EF55
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id BC26D40B850E; Thu,  7 Sep 2017 14:28:31 -0400 (EDT)
Date: Thu, 7 Sep 2017 14:28:31 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Joe Abley <jabley@hopcount.ca>
cc: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
In-Reply-To: <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
Message-ID: <alpine.LRH.2.21.1709071428060.27006@bofh.nohats.ca>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/43MTzgiZYCUIvkeTgq2i35VOT7Q>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 18:28:38 -0000

On Thu, 7 Sep 2017, Joe Abley wrote:

> I hear that. I don't have a strong opinion about whether serving stale data in general is desirable or abhorrent. However, the pragmatist in me says that people are already implementing things like this anyway, and a standard approach is better for all concerned than a fragmented set of uncomfortably-different implementations, which will surely make troubleshooting problems harder.
>
> I also think if a standard specification can be obtained it ought to include appropriate instrumentation to allow a response to indicate whether data is stale or not. This seems to me just one example of a set of additional components we might expect the working group to come up with, which in my mind is a good reason to make it a working group document.
>
> I support adoption with all of that in mind.

Agreed.

Paul


From nobody Thu Sep  7 11:32:33 2017
Return-Path: <vladimir.cunat@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 355C9132940 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 B5EY07sf7iB5 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:32:29 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2712F13263F for <dnsop@ietf.org>; Thu,  7 Sep 2017 11:32:29 -0700 (PDT)
Received: from [192.168.1.101] (nat-34.starnet.cz [178.255.168.34]) by mail.nic.cz (Postfix) with ESMTPSA id 36CC661109; Thu,  7 Sep 2017 20:32:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1504809147; bh=RuXokHujge6ipxp1cyy59M5vrC5N28IaDB4r6jKS+rI=; h=To:From:Date; b=rkKyNnP/lhFN8q7/P9qfNi8C5X3IRbnSaic+tHt2ROLQw9VaS5QkNgXQpPSTgonv3 CGynI5UQC7feUDMCYBOBSueGEtvKzvqAf24d6gOGTKgJ07zYLMDwG2zMbr9zb1u17F bBkgdWod/dptawe6BYzbS0zTb57KrWYOeCYXyAJ0=
Cc: Joe Abley <jabley@hopcount.ca>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
To: dnsop <dnsop@ietf.org>
From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?= <vladimir.cunat+ietf@nic.cz>
Message-ID: <c8a2b763-4a4d-5c9d-4a65-ce7a849574d9@nic.cz>
Date: Thu, 7 Sep 2017 20:32:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TKLvhTH9cmeJznF76pl88x0iJpM>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 18:32:31 -0000

On 09/07/2017 08:25 PM, Joe Abley wrote:
> I also think if a standard specification can be obtained it ought to include appropriate instrumentation to allow a response to indicate whether data is stale or not. This seems to me just one example of a set of additional components we might expect the working group to come up with, which in my mind is a good reason to make it a working group document.

Yes, an interesting idea.  It should be easy to design an EDNS option
that allows to (1) customize some parameters of this (opt-in, opt-out,
request a different client-timeout) and (2) indicate whether some RRs
are stale and perhaps how much stale they are.

--Vladimir


From nobody Thu Sep  7 11:33:26 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E0AC13263F for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jD0CxwInz16Y for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 11:33:24 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8762132F7E for <dnsop@ietf.org>; Thu,  7 Sep 2017 11:33:23 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id m35so1401700qte.1 for <dnsop@ietf.org>; Thu, 07 Sep 2017 11:33:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=eocNpxAog0NFonReZwTPGsY5LfVRhPvlmG0hbQUeils=; b=Z7EvKIaPRwe/Otm1+BwTXgeMlAJz4r/Z9HvOCFJOkOI5iMakTe3m3i4Ubu4KEhkzc4 bWXVxtfKg9zOFj/D0QFQnkNGBkxpGX8GdX2dV8ZQ7hPJqrv8I1PzGzs/q9GqoxkyQ4LI iEVV/awZn8zCI1mO9/4uIB4JlMEgvIXEAuPGrfm/G971csJJ9aWQlWIqZZHV3CYKaLlu t/3HdOyVmVYVBbA2w5DTNwZQJ8/9CpoNmPHXWp6wUzrA6Svus4pH6n8GqqUv5qacBVQj 1kF6zmu9Iok25RwxmUUwOYq9rXnocK+S1T/yME9qleDQJqwJq78tQD9aHDyPGDC+Ddh+ uLrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=eocNpxAog0NFonReZwTPGsY5LfVRhPvlmG0hbQUeils=; b=QYzchA+uJxZ5vjyrIuINHeXrTPksAEsnhXXBY0wQo5yx+WIj7VOfE62hZL49NpBhrN IeD+EyhTogHw6OwdId2+aXUgOtPRMG4ANjLfVzD73vCkWzpvSpDdYn4ttGMowUKJLjtV C21opFl3WYhk5c6cdEDA5iYsLd8i2auukNgHQ563ni5hwEzvvxFX2Cq4C5Fi5DpDF/uK QfWhsCtQefOWxp+nqPZGV5Y6DCdNj8ysRMAlAZAKWn3Mv/+Ok3TxW9zMgszwg3+teuNY DAsE6/UY18t/X8HtW7o67i27126UHQPxraJ/5KVJDFibuSxGW8HWucsWiR+99Ikt79v6 vc9w==
X-Gm-Message-State: AHPjjUijq4GvQIxGqGzXdXAxJEDps39VrCBbKYspgYdPTs3jj0Zlh4Dv 6dl0te0IidpRlBWc0cmBJYO8tNg4Zg==
X-Google-Smtp-Source: AOwi7QAHkduxvVVcOcMVzppU9Q2hGB0w/SN+Fg39D9rQFV2cqlNzUk8LAsBuRbHy1iP5s4Um7Mx7tEThSW0/OgIFecw=
X-Received: by 10.237.60.1 with SMTP id t1mr306985qte.246.1504809202862; Thu, 07 Sep 2017 11:33:22 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.200.54.104 with HTTP; Thu, 7 Sep 2017 11:33:22 -0700 (PDT)
In-Reply-To: <ybltw0emmvh.fsf@wu.hardakers.net>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Thu, 7 Sep 2017 11:33:22 -0700
X-Google-Sender-Auth: 3h-sRYH7hsdvtrgWyPrz_ZG2On0
Message-ID: <CAJE_bqc9zD3Um2oWri7K3L10=MWrUrKpCHpmUGAADKUmFmPYCg@mail.gmail.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VvLF2RMAPAKjlzP90JlnZe10Ypc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 18:33:25 -0000

At Thu, 07 Sep 2017 10:36:50 -0700,
Wes Hardaker <wjhns1@hardakers.net> wrote:

> > I'm not enthousiastic. We should focus on making the DNS
> > infrastructure more reliable, not on adding something to a pile of
> > already fragile protocols.
>
> I don't believe we have any ideas how to make infrastructure more
> reliable in the face of DDoS attacks.

+1.

If we don't work on a proposal like this, I'd love to see a specific
counter proposal that doesn't violate the current protocol
specification (i.e., using a cached answer beyond its TTL) and still
avoids resolution failure when authoritative servers are forced to be
non-responsive due to huge scale DoS attacks.  Otherwise the more
likely scenario is that some vendors still keep a similar protocol
violation using marketing decoration like "smartness" while other
compliant implementors just look incompetent (and this will be a huge
incentive for the latter group to follow the former, and we'll just
see more proliferation of this violation).

--
JINMEI, Tatuya


From nobody Thu Sep  7 13:29:56 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 088CD132FCD for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 13:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 DZmj5KmAWPrp for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 13:29:53 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3274E126DFE for <dnsop@ietf.org>; Thu,  7 Sep 2017 13:29:49 -0700 (PDT)
Received: from localhost.localdomain (104-7-65-172.lightspeed.sntcca.sbcglobal.net [104.7.65.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id B358E61FA2 for <dnsop@ietf.org>; Thu,  7 Sep 2017 20:29:48 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Date: Thu, 07 Sep 2017 13:29:47 -0700
Message-ID: <8295055.TIQDDEhZcU@localhost.localdomain>
Organization: Vixie Freehold
User-Agent: KMail/4.13.0.25 (Linux/4.12.9-200.fc25.x86_64; KDE/4.14.30; x86_64; ; )
In-Reply-To: <ybltw0emmvh.fsf@wu.hardakers.net>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CrSsxdVVK5QIMmb14zvi25xYXNw>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 20:29:55 -0000

there will be two replies here. one to wes, one to joe.

On Thursday, September 07, 2017 10:36:50 AM Wes Hardaker wrote:
> Stephane Bortzmeyer <bortzmeyer@nic.fr> writes:
> > I'm not enthousiastic. We should focus on making the DNS
> > infrastructure more reliable, not on adding something to a pile of
> > already fragile protocols.
> 
> I don't believe we have any ideas how to make infrastructure more
> reliable in the face of DDoS attacks.  Is your opinion then that
> everyone should be using a DDoS resilient cloud provider in case they
> ever get attacked?

i dislike the form of the second sentence, so i'll restrict my answer to your 
first sentence alone. if i were to take the question in your second sentence 
literally, my answer would be simply, yes. but that would be misleading as to 
my actual values and true intentions.

i agree that we don't have ideas on how to make infrastructure more reliable 
in the face of ddos attacks. having authored the cut-down simplified pointy-
haired-boss version of BCP38 (which we called SAC004) and having spent a 
decade on airplanes trying to get folks to understand what source address are, 
why bad guys like to spoof them, and why good guys aren't properly positioned 
or incentivized to verify them... i sort of gave up and assumed that the 
internet was just never going to be dependable. that is to say, any time some 
angry teenager wants something to be down, it will be down. exceptions include 
facebook and google, who have invested literally tens of billions of dollars 
in scalable defensible infrastructure.

i could have predicted that others who realized this fundamental unshakable 
and dark truth would behave otherwise -- not, in other words, simply give up. 
i urge you to reconsider whether adding more signaling and more state to a 
system that already has more than we can comprehend, is your best way forward. 
in fact, please consider the possibility that you are following a recipe for 
disaster, where by trying to solve the problems you have today, you must and 
will inevitably create worse problems for tomorrow, which will be even harder 
to identify much less to solve.

see also:

http://queue.acm.org/detail.cfm?id=1242499

---

On Thursday, September 07, 2017 02:25:14 PM Joe Abley wrote:
> On 7 Sep 2017, at 11:42, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> > I'm not enthousiastic. We should focus on making the DNS
> > infrastructure more reliable, not on adding something to a pile of
> > already fragile protocols.
> 
> I hear that. I don't have a strong opinion about whether serving stale data
> in general is desirable or abhorrent. However, the pragmatist in me says
> that people are already implementing things like this anyway, and a
> standard approach is better for all concerned than a fragmented set of
> uncomfortably-different implementations, which will surely make
> troubleshooting problems harder.

joe, i'd be ready to agree, except that ECS was standardized here under the 
same (precisely the same) reasoning, and as you'll recall, i lost my bid to 
have an applicability statement included, to the effect that this practice is 
common, but not necessarily recommended, and in fact somewhat controversial.

unless you can show how a standard for using stale data, published by the 
IETF, will not have an imprimatur such that newcomers believe that there are 
no downsides to implementing it, then i must respectfully disagree that having 
a standard would be better than having chaos.

> I also think if a standard specification can be obtained it ought to include
> appropriate instrumentation to allow a response to indicate whether data is
> stale or not. This seems to me just one example of a set of additional
> components we might expect the working group to come up with, which in my
> mind is a good reason to make it a working group document.
> 
> I support adoption with all of that in mind.

if the draft being considered was clear on two points, i'd support adoption.

first, this feature is controversial, and there is not consensus favouring its 
implementation, merely its documentation.

second, the initiator must indicate its intent to use data beyond its TTL, and 
the responder must assent to this, and that otherwise, including in the 
default case where such signaling is absent, data shall not be used beyond its 
TTL.

vixie


From nobody Thu Sep  7 13:43:17 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEE3132FDD for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 13:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 8D6jy3UrNxo4 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 13:42:50 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51BFA132FDB for <dnsop@ietf.org>; Thu,  7 Sep 2017 13:42:46 -0700 (PDT)
Received: from localhost.localdomain (104-7-65-172.lightspeed.sntcca.sbcglobal.net [104.7.65.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 3318061FA2 for <dnsop@ietf.org>; Thu,  7 Sep 2017 20:42:46 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Date: Thu, 07 Sep 2017 13:42:45 -0700
Message-ID: <8826934.gJBl6qSRLR@localhost.localdomain>
Organization: Vixie Freehold
User-Agent: KMail/4.13.0.25 (Linux/4.12.9-200.fc25.x86_64; KDE/4.14.30; x86_64; ; )
In-Reply-To: <CAJE_bqc9zD3Um2oWri7K3L10=MWrUrKpCHpmUGAADKUmFmPYCg@mail.gmail.com>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <ybltw0emmvh.fsf@wu.hardakers.net> <CAJE_bqc9zD3Um2oWri7K3L10=MWrUrKpCHpmUGAADKUmFmPYCg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qUANGYhCyuPt_4ar5kuupnO6LYg>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 20:42:52 -0000

On Thursday, September 07, 2017 11:33:22 AM =E7=A5=9E=E6=98=8E=E9=81=94=
=E5=93=89 wrote:
> ...
>=20
> If we don't work on a proposal like this, I'd love to see a specific
> counter proposal that doesn't violate the current protocol
> specification (i.e., using a cached answer beyond its TTL) and still
> avoids resolution failure when authoritative servers are forced to be=

> non-responsive due to huge scale DoS attacks.

i think the actual problem statement is broader, and that by solving fo=
r this=20
narrow version, we would lose the complexity/capability tradeoff -- we'=
d add=20
more state and more signaling at a cost higher than what we would get f=
or it.

it's a general reachability problem not specifically ddos problem. reas=
ons for=20
not being able to refresh data in a cache include ddos, but also backho=
es,=20
wire cutters, squirrels, circuit breakers, and bad design/provisioning.=


i think the right answer will look like a miniature version of IXFR/AXF=
R and=20
NOTIFY, such that a cache can register its intent to become a partial s=
tealth=20
secondary server, and by participating, an authority server can both in=
dicate=20
its willingness to have this done, and possibly remember what was trans=
mitted=20
so as to facilitate subsequent cache invalidation or zone change notifi=
cation=20
messaging. one could even imagine a dns cookie exchange at the outset, =
to help=20
authenticate later messages. sort of a super-lightweight session protoc=
ol.

when the DNS was first popularized, we were using a lot of computers wi=
th less=20
than four megabytes of memory and fewer than a million instructions per=
=20
second, and our links were thought fast if 56K DDS, or super-fast if 1.=
544M T1=20
or even 2.0M E1. this drove choices of how to encode, how to compress, =
where=20
to synthesize, and whether to authenticate. all of those choices should=
 be up=20
for reconsideration now.

if our _vision_ as a technical community is to have little chunks of se=
mi-
authoritative data cached in stealth-like secondary-like places, and th=
en kept=20
up to date, then we should pursue that, because moore's law and the=20
privatization and commercialization of the internet have made it now=20=

practical.

if we lack a vision and we're going to pursue small discrete targets of=
=20
opportunity based on the business problems faced by each industry parti=
cipant,=20
then we'd be making hairball soup, and i'd ask that we not.

see also:

http://queue.acm.org/detail.cfm?id=3D1647302

vixie


From nobody Thu Sep  7 14:20:30 2017
Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A6A127005 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 14:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oVmFjNqk4F5D for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 14:20:22 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B4AA132F93 for <dnsop@ietf.org>; Thu,  7 Sep 2017 14:20:22 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id r141so2295754qke.2 for <dnsop@ietf.org>; Thu, 07 Sep 2017 14:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pvrNI0Gr8mY3lmE73q+7G5fyrkpxshRCxQvZy4C/6jE=; b=jnYT8CtgOaWPFOWyR1crkZ/UznOO7YasjHk1XmOMfWsPb+4St7eARRVms7hkKTxSFV lWpaE39TjtXtekFLl7pXz7VisZMAHkkyfGePFXkUex4JJB0UHqLfrmSRPTghzuDwQe5r dr6RURsOd7g/NHfPm0HJNme2sJc2FhrB2M8k+OV/zF3tJ2EtkJ+xE6YABi0EwLbms5KW SjGliegdytzx6psuyf24k7YxpI8oLEqGgVMtGgM05L7jzfBGr3/pBc2NStDe22f4PUoz iwUiY6zewueW/7Ub0GKQRxsbrbdi/BU7rnZI7q37Weguta0Uhxi+sWh75e/KrZhEOBYB r6BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pvrNI0Gr8mY3lmE73q+7G5fyrkpxshRCxQvZy4C/6jE=; b=HKrKsWruv6NNp+UkxdlE74L8GiErImISuYv4CwHPQvJ4rKiR1adlOFspnaQNlgVRRZ ri6sb2foJHimVTEto+lQFLMN0SsIRD0r88k1xGgYdypWWVaZxykB+Fsf1yrxx+pfMOYF R7zSqG7KaGT3XtB57paDeXxEEWRKtQ3Af8mR4TfkLpk0El/eVzGv5T/FsygvFDst/MqN I63SrMRaASjNxRqx5Q/Ux94Zt+dcJzQj4YodpKJjkBkQNlthI4rRHbxMouyQ3YR3V8p2 DRKQW89qmdrVGbhaqTakNiTAWrJOxZzLNDzm52DeiB4NbZMNCWLwPAB1Mt2mFUIWNTXM AeHg==
X-Gm-Message-State: AHPjjUiKlSOCdjFXmPocLutVF8/dbZ7Wh+qIxMNd5zG1CdkbzMJEFGGp 0eTnKCj+J9ErfA==
X-Google-Smtp-Source: AOwi7QA8Lj4ugiVpv/baAbqgnAJLweK9L8gZ7+hqeeXBASZpPJ5oennUxf7hEqXoifFZ71ufalWMQQ==
X-Received: by 10.55.101.23 with SMTP id z23mr914775qkb.257.1504819221250; Thu, 07 Sep 2017 14:20:21 -0700 (PDT)
Received: from [10.0.0.22] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by smtp.gmail.com with ESMTPSA id p7sm191896qke.78.2017.09.07.14.20.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 07 Sep 2017 14:20:20 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20170907143239.x4out34m7weaah2u@nic.fr>
Date: Thu, 7 Sep 2017 17:20:18 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <39E9CCCB-6BEB-47DE-87FB-CD45E7FC84E6@gmail.com>
References: <20170907143239.x4out34m7weaah2u@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Op6FQJFxWrVtrvirvTOLnLvPqxQ>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 21:20:29 -0000

On Sep 7, 2017, at 10:32 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> draft-wkumari-dnsop-internal-00 proposes to reserve .internal for
> RFC1918-like domain names. There is clearly a strong demand for that.
> (There is also a strong demand for happy sex, great food, excellent
> wines and diamong rings, but let's ignore it for the moment).
>=20
> The document clearly documents that it will not happen, since it
> requires an entire new process at ICANN.

As WG chair: no reason I know of to assume this.=20

As long-time observer of IETF and ICANN process: no reason I know of to =
assume this; such a request from the IETF, however, would involve the =
IESG (presumably armed with IETF consensus), the IAB (which manages the =
IETF liaison relationship with ICANN on behalf of the IETF), and some =
patience, since it amounts to a request that the ICANN community do work =
to accommodate a need of the IETF. This doesn't mean it can't be done or =
even that it won't be done, only that the implications need to be =
considered as far as possible.=20

At the very least, I'd like to see an extremely strong rationale for =
making such a request; we should be working towards a statement =
something like "doing this solves the following large class of problems =
for a really long time, in a demonstrably better way than any of the =
alternatives."

> Also, it may be a good idea to add an "Internationalization
> considerations" section. If people want a memorable domain name (and
> not, say, the TLD .693268ed5948276cb48c3f3339ac465d, which would work
> as well), it's because it is typable and rememberable), they may want
> it in other languages.

Agreed. This mechanism is intended, at least in part, to accommodate the =
common desire people seem to have for DNS names to act sort of like =
natural language objects and not just random strings. It seems to me =
that defining such a mechanism should consider the likelihood that not =
everyone who wants to use it will be native speakers of English who are =
happy to limit the available characters to US-ASCII.


Suzanne


From nobody Thu Sep  7 15:03:33 2017
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68BF1132FE7 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.com
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 S8zDrsd9eY7y for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:03:28 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A479D132FEC for <dnsop@ietf.org>; Thu,  7 Sep 2017 15:03:28 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id m142so1462148vkf.2 for <dnsop@ietf.org>; Thu, 07 Sep 2017 15:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=StoeH0qHSimAeZxQOBcxIPMQTpNCRYpFIPUhatDwBAM=; b=JdSeHzoXZ/ehmJCBu5SFO96orwRpKb/mvJR+Gqy2NTuQt5ihz7dMIgTpIuab1iCB11 Ica1uTPRe7A3LN+2ilbuCrczMRdJa+d4tRAzVV0W9cLttqyNMy37t1yIhEqqwX93wZ30 OYBwM8+MbYVSqRJGQmdLZzM447JggEPVLSoVJAt2giL3GpTcpgmbbJM+MqlkGno9G0+U KBl0UcNt3+xgoO15bpgprHQH10rcbdIqxFbKZkGfyEvSU8ai9Mgh00IT0si/7T6EL7MS 9OxxZi5Ce7mfLFCD1KfBL5EGwKn2Hel9FG/19xiOF1R5Pz5XrmSk9JYZNICjST9ZvHrl ZRTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=StoeH0qHSimAeZxQOBcxIPMQTpNCRYpFIPUhatDwBAM=; b=JnIS/4RTFLjX9int4pf7lyJNVjy9cq09pPCA3dXydXnpSb5i/fQBZyxTSUuxy5ZmqJ HIHy+du1F8pQjJ06sUXHfeHrDVr8IgQLIkMHdJ/uhzuqaLkeeO+iUdVqJ2SHwg2/OTQw luKHB0T2xYKJX5/Edb5vDSXiflPCihwF3e2KIRGj9nOyjS6kZgt8wPi8U5liTPsFxZe5 EZHUs1WArloJB0BiNbLnkCNjCq2hIa+zUn4tAaxKnc9MDlVdpA5x7Q8ku2ue4VLAIQAt EGgKTFTQblYbXPxMeE7pxvsOLhs7I40bJ0Q/scImL/eNz1BmVtqIjbOyNJflf5oEpgit BU3g==
X-Gm-Message-State: AHPjjUhO6yNlH5B4aJC6o+dQWa8XGNBwh3aRRWcUUBbBU1vlP8KTx9OB MoYjitpAcYSLU/vwrRUA/sw63oiQtm3xe74=
X-Google-Smtp-Source: AOwi7QCYaLSKYuvxsSiKdZ1j4a+eseh9pen9lDyzwlEgOwUkNywg70/VLN6EhhB1Fw/khQ0ZKGOaBU5UYRXDZ7KYc18=
X-Received: by 10.31.63.204 with SMTP id m195mr500367vka.111.1504821807450; Thu, 07 Sep 2017 15:03:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.78 with HTTP; Thu, 7 Sep 2017 15:03:27 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:80cf:4544:2cf8:7f7d]
In-Reply-To: <8826934.gJBl6qSRLR@localhost.localdomain>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <ybltw0emmvh.fsf@wu.hardakers.net> <CAJE_bqc9zD3Um2oWri7K3L10=MWrUrKpCHpmUGAADKUmFmPYCg@mail.gmail.com> <8826934.gJBl6qSRLR@localhost.localdomain>
From: George Michaelson <ggm@algebras.org>
Date: Fri, 8 Sep 2017 08:03:27 +1000
Message-ID: <CAKr6gn1rF1BphX3iQ3_HkrOLZBLR0uKo-uiaWD_pUgCEonCzkg@mail.gmail.com>
To: dnsop WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JRPOz7imHEY_0vJ_8hXVDG2HhOI>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 22:03:32 -0000

add client-intent signalling, and irrespective add server signalling
of action, and I could be there.

I'd support adoption.

On Fri, Sep 8, 2017 at 6:42 AM, Paul Vixie <paul@redbarn.org> wrote:
> On Thursday, September 07, 2017 11:33:22 AM =E7=A5=9E=E6=98=8E=E9=81=94=
=E5=93=89 wrote:
>> ...
>>
>> If we don't work on a proposal like this, I'd love to see a specific
>> counter proposal that doesn't violate the current protocol
>> specification (i.e., using a cached answer beyond its TTL) and still
>> avoids resolution failure when authoritative servers are forced to be
>> non-responsive due to huge scale DoS attacks.
>
> i think the actual problem statement is broader, and that by solving for =
this
> narrow version, we would lose the complexity/capability tradeoff -- we'd =
add
> more state and more signaling at a cost higher than what we would get for=
 it.
>
> it's a general reachability problem not specifically ddos problem. reason=
s for
> not being able to refresh data in a cache include ddos, but also backhoes=
,
> wire cutters, squirrels, circuit breakers, and bad design/provisioning.
>
> i think the right answer will look like a miniature version of IXFR/AXFR =
and
> NOTIFY, such that a cache can register its intent to become a partial ste=
alth
> secondary server, and by participating, an authority server can both indi=
cate
> its willingness to have this done, and possibly remember what was transmi=
tted
> so as to facilitate subsequent cache invalidation or zone change notifica=
tion
> messaging. one could even imagine a dns cookie exchange at the outset, to=
 help
> authenticate later messages. sort of a super-lightweight session protocol=
.
>
> when the DNS was first popularized, we were using a lot of computers with=
 less
> than four megabytes of memory and fewer than a million instructions per
> second, and our links were thought fast if 56K DDS, or super-fast if 1.54=
4M T1
> or even 2.0M E1. this drove choices of how to encode, how to compress, wh=
ere
> to synthesize, and whether to authenticate. all of those choices should b=
e up
> for reconsideration now.
>
> if our _vision_ as a technical community is to have little chunks of semi=
-
> authoritative data cached in stealth-like secondary-like places, and then=
 kept
> up to date, then we should pursue that, because moore's law and the
> privatization and commercialization of the internet have made it now
> practical.
>
> if we lack a vision and we're going to pursue small discrete targets of
> opportunity based on the business problems faced by each industry partici=
pant,
> then we'd be making hairball soup, and i'd ask that we not.
>
> see also:
>
> http://queue.acm.org/detail.cfm?id=3D1647302
>
> vixie
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Thu Sep  7 15:12:44 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEE713235C for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 I0F3p0ggq4pK for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:12:41 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id C585E13235A for <dnsop@ietf.org>; Thu,  7 Sep 2017 15:12:41 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id 71254540D94; Thu,  7 Sep 2017 18:12:41 -0400 (EDT)
Date: Thu, 7 Sep 2017 18:12:41 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
Message-ID: <20170907221241.GA1031@puck.nether.net>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net> <8295055.TIQDDEhZcU@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8295055.TIQDDEhZcU@localhost.localdomain>
User-Agent: Mutt/1.9.0 (2017-09-02)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_O6fTuGOQ5En2h4Xoi_AB-a1sfc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 22:12:43 -0000

On Thu, Sep 07, 2017 at 01:29:47PM -0700, Paul Vixie wrote:
> if the draft being considered was clear on two points, i'd support adoption.
> 
> first, this feature is controversial, and there is not consensus favouring its 
> implementation, merely its documentation.
> 
> second, the initiator must indicate its intent to use data beyond its TTL, and 
> the responder must assent to this, and that otherwise, including in the 
> default case where such signaling is absent, data shall not be used beyond its 
> TTL.

	Would you see the querying application informing you of intent via 
option code saying "If I'm unable to talk to you once TTL expires, I may serve 
your last known good answer"?

	What would a server then do if this intent were known?  serve some
alternate data, or even return REFUSED?  I could see sending a secure notify
to anyone who requested the QNAME after change, but holding this state may
end up with complexity similar to what's some have seen with ECS.

	- Jared


-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.


From nobody Thu Sep  7 15:13:41 2017
Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6E4C132F56 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.com
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 HwbhHOc4Pd7A for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 15:13:39 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5192A13235A for <dnsop@ietf.org>; Thu,  7 Sep 2017 15:13:39 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id o22so1510155vke.1 for <dnsop@ietf.org>; Thu, 07 Sep 2017 15:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yt+0EZ6darj4x6XMaIxop94Qcp7tNdv8bHFMXIF8D/I=; b=FicwVQpUlG1jSvqjhBIN3Wer5yrf8Noh9w/l0bWj3hEkmG/1rhhwWA8DFAxbXa2jxB gwUasTAvrwCGo+VXUcAr/y9x22MM3jYCBt/MEmxRPDGCID6Tt49UNuXYp4TtcbVcf6Ap hMbVGMAy44WELy66STw0ICDu5DJRpbebL0fxAl5fXKk+l/X+5aJSSqwJmLx7eG3LbsEU M+gNNsHqUMGd93hblHNhb3g/qQqK3q9cZfBHIgek9AgeH3hVZaBbCy6bubgQZqv/RvYy YPSC/RqVdT4gqVDD94f+C0VQRpvht47PMRwzXP/MC+2ehuE3+Sa0qnSHT2ze5pTqY4wL nvNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yt+0EZ6darj4x6XMaIxop94Qcp7tNdv8bHFMXIF8D/I=; b=hwtTXjuJ1/5w+g+PEv79Qd/2pYrsFRfDSFkLaD/0aYpYA3XHFc355rLRjS4M22uN1u YnVIZqAhM6UEnIMQSAuiMyyP7gWC8ZAxZuHVJyHCwR2AUErNO+P2omFIN2XoGIU2IifL 1T4+/NXGh0p4Mi4fz069pWtrZ2zbfJzEJEvDEUqJhwFzY1alpQLUJknD91SX2ATMXokV iHZWrcmIiixyoCeXV86Jf9XGxvLyTC+eAHyDHAWDIt1eypFXuOq6KYvdJzh0otBUVbkB yycDY6PD6LUCo/oqfzlxUdjSGD+edRXrFezRPJIUajVmAhVMRodkBtNiYqthRGbll7cC xKzw==
X-Gm-Message-State: AHPjjUiExSPBvaa1pl/IPVJGL14s1HPovHAogVRZYLyl1Vbzl59wUStV hj3l9gBUei6V8kl9F7kZPGyVuT+BKf+Y3Uw=
X-Google-Smtp-Source: AOwi7QD8YeAZ8JQ9KayWPEWOhRDzlc3Kj0JnW6nYWvLTN3wDru0hXBfbyD6FTN1+ekcOa6ntJOs8/8g4UeOAitJE+dI=
X-Received: by 10.31.63.204 with SMTP id m195mr517091vka.111.1504822418503; Thu, 07 Sep 2017 15:13:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.78 with HTTP; Thu, 7 Sep 2017 15:13:38 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:80cf:4544:2cf8:7f7d]
In-Reply-To: <20170907143239.x4out34m7weaah2u@nic.fr>
References: <20170907143239.x4out34m7weaah2u@nic.fr>
From: George Michaelson <ggm@algebras.org>
Date: Fri, 8 Sep 2017 08:13:38 +1000
Message-ID: <CAKr6gn2DSFO1E_p7jcyp2NPFbTL_6JvnRgL3z0E0NeuNnWUeoQ@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gqZ5xzb2wlXr80BGCRyj31mbygA>
Subject: Re: [DNSOP] Remarks about draft-wkumari-dnsop-internal-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 22:13:40 -0000

It's not sensible to presume the action of an independent
decision-making body. It's sensible to discuss it, but it should only
inform our own process logic, not decide it categorically (I think)

I might share your expectation of the outcome, but I would hesitate to
reject a draft on a supposition.

-George


From nobody Thu Sep  7 17:06:07 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AFA7133044 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 17:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VWXDNoGhlU-n for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 17:06:06 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F010B133041 for <dnsop@ietf.org>; Thu,  7 Sep 2017 17:06:05 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 8092734B5CC; Fri,  8 Sep 2017 00:06:02 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5BBF216008F; Fri,  8 Sep 2017 00:06:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3F88216008E; Fri,  8 Sep 2017 00:06:02 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TPTmt3ZDA6es; Fri,  8 Sep 2017 00:06:02 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id BD618160073; Fri,  8 Sep 2017 00:06:01 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id DDBD7849CFAC; Fri,  8 Sep 2017 10:05:59 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: Warren Kumari <warren@kumari.net>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org> <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>
In-reply-to: Your message of "Thu, 07 Sep 2017 09:23:29 -0400." <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>
Date: Fri, 08 Sep 2017 10:05:59 +1000
Message-Id: <20170908000559.DDBD7849CFAC@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/C5xc59KyhLKNeH1xhr9b1Z84FUE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 00:06:07 -0000

In message <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>, Ted Lemon writes:
> 
> On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
> > I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
> > tools.  Lookups should "just work" like they did before the root
> > zone was signed.
> 
> Because...?

Because there are things you can do with localhost as a DNS zone
that you can't do with /etc/hosts, NIS, etc. as they are limited
to addresses only.

Localhost should work just like home.arpa.  The tools we use shouldn't
need special knowledge.  Special knowledge means EVERYTHING needs
to be tested to see if it works with localhost as well and regular
names.  That testing will get missed.  If it doesn't get missed it
costs more money.  Workarounds for different behavior increases the
probability of bugs being introduced as there will be seperate code
paths.

If I want to add a local trust anchor for localhost I will then
need additional code to disable the workaround for the fact the
root doesn't have a insecure delegation.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep  7 18:37:49 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013C6132F2F for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 18:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 whL6scOrtyuS for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 18:37:46 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68AD412426E for <dnsop@ietf.org>; Thu,  7 Sep 2017 18:37:46 -0700 (PDT)
Received: from [172.31.99.4] (50-76-63-241-ip-static.hfc.comcastbusiness.net [50.76.63.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 472BE61FA2 for <dnsop@ietf.org>; Fri,  8 Sep 2017 01:37:45 +0000 (UTC)
Message-ID: <59B1F467.9010308@redbarn.org>
Date: Thu, 07 Sep 2017 18:37:43 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: dnsop@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rHiNaABoTwDtPfWMPgZKoJ9gY9I>
Subject: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 01:37:48 -0000

note, there's a proposal contained here.

Jared Mauch wrote:
> On Thu, Sep 07, 2017 at 01:29:47PM -0700, Paul Vixie wrote:
>> if the draft being considered was clear on two points, i'd support adoption.
>>
>> ...
>
> 	Would you see the querying application informing you of intent via
> option code saying "If I'm unable to talk to you once TTL expires, I may serve
> your last known good answer"?

i don't think so. if it was "may i serve your last good answer?" then 
yes. but with it as "i may" and the ? outside the quotes as shown above, 
then no.

> 	What would a server then do if this intent were known?  serve some
> alternate data, or even return REFUSED?  I could see sending a secure notify
> to anyone who requested the QNAME after change, but holding this state may
> end up with complexity similar to what's some have seen with ECS.

this whole approach is incredibly unappealing. as i wrote to jinmei earlier:

> i think the actual problem statement is broader, and that by solving for this
> narrow version, we would lose the complexity/capability tradeoff -- we'd add
> more state and more signaling at a cost higher than what we would get for it.
>
> it's a general reachability problem not specifically ddos problem. reasons for
> not being able to refresh data in a cache include ddos, but also backhoes,
> wire cutters, squirrels, circuit breakers, and bad design/provisioning.
>
> i think the right answer will look like a miniature version of IXFR/AXFR and
> NOTIFY, such that a cache can register its intent to become a partial stealth
> secondary server, and by participating, an authority server can both indicate
> its willingness to have this done, and possibly remember what was transmitted
> so as to facilitate subsequent cache invalidation or zone change notification
> messaging. one could even imagine a dns cookie exchange at the outset, to help
> authenticate later messages. sort of a super-lightweight session protocol.
>
> when the DNS was first popularized, we were using a lot of computers with less
> than four megabytes of memory and fewer than a million instructions per
> second, and our links were thought fast if 56K DDS, or super-fast if 1.544M T1
> or even 2.0M E1. this drove choices of how to encode, how to compress, where
> to synthesize, and whether to authenticate. all of those choices should be up
> for reconsideration now.
>
> if our _vision_ as a technical community is to have little chunks of semi-
> authoritative data cached in stealth-like secondary-like places, and then kept
> up to date, then we should pursue that, because moore's law and the
> privatization and commercialization of the internet have made it now
> practical.

in other words i'd like to solve both partitioning/reachabilities not 
just one. not just "i can't reach a remote server due to a partition" 
but also "i can't learn the role and address of nearby servers due to a 
partition". i guess you could call it "opportunistic semi-authoritative 
caching".

the heuristic for deciding what to cache is probably popularity, but 
also, NS/A/AAAA chains, and also, the full contents of the root zone.

it would only be allowed if dns cookies were exchanged, since i don't 
think we should spam people with notifies after receiving a spoofed 
source stealth-service request.

the desire to stealth-serve would be encoded in an EDNS option bit, 
which if answered in the affirmative, would lead to a REQUEST-NOTIFY 
message that specified the RR-NAME of interest, and an enum saying 
whether it's all RR-SETs there, or just a couple of them, or whether 
it's the whole zone.

this would be in-band content monitoring. a "push" form of DNS. it would 
solve two disconnection problems (distant server unreachable, and also, 
nearby server unidentifiable). it would solve the "root servers might be 
ddos'd or otherwise unreachable" problem without any of the 
configuration hackery specified in RFC 7707. it would not lead to stale 
data. it would not require detailed DNS or server knowledge by an rdns 
operator. in fact it could be put into the middleboxes (wifi, cable, 
dsl) who insist on doing RDNS service now.

it could even be integrated with forwarding.

moore's law, and the internet economy, have been kind. let's use the 
resources we've been given, to come up with a DNS that actually does 
what we want, and doesn't add more static configuration state.

-- 
P Vixie


From nobody Thu Sep  7 19:07:19 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C257F133095 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 sVWUbRCqI_rK for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:07:15 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964B1133093 for <dnsop@ietf.org>; Thu,  7 Sep 2017 19:07:15 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 3BB9034AFA8 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:07:13 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 25277160045 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:07:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0FBFA160046 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:07:13 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WK7xo2J6bRab for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:07:12 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id B1E3E160045 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:07:12 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 0170284A3195 for <dnsop@ietf.org>; Fri,  8 Sep 2017 12:07:09 +1000 (AEST)
To: dnsop@ietf.org
From: Mark Andrews <marka@isc.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net> <8295055.TIQDDEhZcU@localhost.localdomain> <20170907221241.GA1031@puck.nether.net>
In-reply-to: Your message of "Thu, 07 Sep 2017 18:12:41 -0400." <20170907221241.GA1031@puck.nether.net>
Date: Fri, 08 Sep 2017 12:07:09 +1000
Message-Id: <20170908020710.0170284A3195@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/faRjxlEvhLhREaHzQtvx2K326ro>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 02:07:17 -0000

Part of the problem is that we have one TTL value for both freshness
and don't use beyond.

This is fixable.  It is possible to specify two timer values.  It
does require adding signaling between recursive servers and
authoritative servers, on zone transfers and update requests.

You basically add a additional timer field to every record immediately
after the TTL field.  This is only returned if the client has
signalled support for the extended field, I suggest using the last
DNS header bit for this as you can determine how you will parse the
response base on whether the bit is set in the response or not.
This field is used to expire records from the cache and its value
is set to the TTL field if the server has learnt the record from
server that doesn't support the extension.

The existing TTL field is used for freshness checking.  When a query
comes in after that value has expired a freshness check is performed
similar to the existing prefetches that happen today.  A TTL of 1
is returned unless the original TTL was 0 in which case 0 is returned.

New client - new recursive server - new authservers

	example.com. 300 86400 IN A 1.2.3.4

		+300 seconds

	example.com. 1 86100 IN A 1.2.3.4
	 (background query is in process)

Old client - new recursive server - new authservers

	example.com. 300 IN A 1.2.3.4

		+300 seconds

	example.com. 1 IN A 1.2.3.4
	 (background query is in process)

New client - new recusive server - old auth servers

	example.com. 300 300 IN A 1.2.3.4

		+300 seconds
	 (record has expired from cache,
	  new query is performed)

	example.com. 300 300 IN A 1.2.3.4

For UPDATE a replacement opcode would be cleanest way to signal the
new format is being used.  NOTIMP should be returned by servers
that don't support the new opcode.

There will be a few broken servers that just echo back the new
header bit.

This way the authoritative servers still control how long records
are stored for.  Dead servers will get a little bit of traffic until
the the refresh completes.  If the authorative servers are under
attack the clients still see a answer.

The alternative is to perform the refresh query and if it fails to
complete within X milliseconds return the cached data rather than
returning the cached data and doing the refresh in the background.

Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep  7 19:17:47 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E198913308C for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 6MzarJTpH7Rr for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:17:44 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12826132D62 for <dnsop@ietf.org>; Thu,  7 Sep 2017 19:17:44 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id e199so2340284pfh.3 for <dnsop@ietf.org>; Thu, 07 Sep 2017 19:17:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xkB9G4PVjMDSEbzEGDN7PEztz4NJ8MDC6wgJFFoG1Ig=; b=svIbOxHTxk/c8n05Se7PIA3ScqEfuSEgIRG+vvrSW69+tP4gNKb1DhlOJ6srtVt09X e26eZ4g2n/Q96T1w0Z9vP3hjvTnLe7oRx9Y8ym2T8n6+i3WauDS3/8FAvx/sZc0FvIzQ LspvOoWdwRdnPwZ0MdSljQawSa0SeGCqD/GuLgxkS7C6eNk/A0WgLx4NzaO7ObBzvn5b Ev1A+nqg0dMmpjWcqQkkI8eCekjl5VsLQ6hSPAnkW0b1+SDnisUIvX9V8RqYxnj8fFg/ fzXWBqEQkq2o8nT+NvviuSuDGAmi5LCfn+ZrE+DrDXnnzWDBlhae0X1skpDi/m/Ho1kj Dm2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xkB9G4PVjMDSEbzEGDN7PEztz4NJ8MDC6wgJFFoG1Ig=; b=gZXu6djdvpCA1MIb1A/zLgs1Ghew5C4RmZHG1eqcwYKM1GTK608gJ2e3TNhSOFGjna uKRh8Ld3JHcAJ7x6yFY7uOVx+kCGNe23fTJD8PiJVC3cxt8RoNP73J5ZUPHKxD/fvvYE Pexao4wvKTdrltq8g+s96BP91XImA15ilw7NV66hBPRxmLFjf1r5TjnQR50giyJVEHnm NUQWPoM4G/NBoPhHd4S0zHk2/G1hjHCdDD+NEHnMmtmYmE+CAgffZ2xjxv+p/8XaR6J+ vPoM7JymttreH6gRjuvXuuPpl7mg/Z36I4I2VtbOTL1k5InmpuHJ3VybNIhXvSWZcK8Z scZQ==
X-Gm-Message-State: AHPjjUhv2hsylsKrwNIt7MoicfglByW7GREyY2rQQ8dy240WoRg0EGxl q2R/U0PX4EWuP0oEyJvNyXVrrHAZ3PqG
X-Google-Smtp-Source: ADKCNb595wSw84KKG0yHacrKDIg+kFlJpPlxWDYxHVbrqxwe/+SbyMEcL5CfwU8DsjrYg1IjSMjSSOVEWVkEZB4dqD4=
X-Received: by 10.99.95.147 with SMTP id t141mr1526124pgb.340.1504837063521; Thu, 07 Sep 2017 19:17:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.152.98 with HTTP; Thu, 7 Sep 2017 19:17:42 -0700 (PDT)
Received: by 10.100.152.98 with HTTP; Thu, 7 Sep 2017 19:17:42 -0700 (PDT)
In-Reply-To: <20170908000559.DDBD7849CFAC@rock.dv.isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org> <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com> <20170908000559.DDBD7849CFAC@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Sep 2017 22:17:42 -0400
Message-ID: <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: dnsop WG <dnsop@ietf.org>, Warren Kumari <warren@kumari.net>, Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c05f4ca9dd1520558a42ee2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aFf9FJqWxJdtgc1kaULJuIqg6dM>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 02:17:46 -0000

--94eb2c05f4ca9dd1520558a42ee2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The discussion had covered the failure mode problem. There is substantial
agreement that it's better for a stub that issues a query for localhost to
fail than to succeed. You seem to disagree.

You haven't stated a reason for disagreeing=E2=80=94instead you've vigorous=
ly
asserted that this is true. It's fine for you to do this, but if you were
to get your way, that would be exactly the bad outcome I want to avoid.

So if there really is a problem here, it would be good for you to make it
clear. Your stated desire to preserve flexibility makes sense to me, but it
doesn't contradict the reason already given for *not *providing that
flexibility.

Is there some *other* reason why this is important to you, or is that it?

On Sep 7, 2017 8:06 PM, "Mark Andrews" <marka@isc.org> wrote:

>
> In message <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>, Ted Lemon
> writes:
> >
> > On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
> > > I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
> > > tools.  Lookups should "just work" like they did before the root
> > > zone was signed.
> >
> > Because...?
>
> Because there are things you can do with localhost as a DNS zone
> that you can't do with /etc/hosts, NIS, etc. as they are limited
> to addresses only.
>
> Localhost should work just like home.arpa.  The tools we use shouldn't
> need special knowledge.  Special knowledge means EVERYTHING needs
> to be tested to see if it works with localhost as well and regular
> names.  That testing will get missed.  If it doesn't get missed it
> costs more money.  Workarounds for different behavior increases the
> probability of bugs being introduced as there will be seperate code
> paths.
>
> If I want to add a local trust anchor for localhost I will then
> need additional code to disable the workaround for the fact the
> root doesn't have a insecure delegation.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

--94eb2c05f4ca9dd1520558a42ee2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">The discussion had covered the failure mode problem. Ther=
e is substantial agreement that it&#39;s better for a stub that issues a qu=
ery for localhost to fail than to succeed. You seem to disagree.<div dir=3D=
"auto"><br></div><div dir=3D"auto">You haven&#39;t stated a reason for disa=
greeing=E2=80=94instead you&#39;ve vigorously asserted that this is true. I=
t&#39;s fine for you to do this, but if you were to get your way, that woul=
d be exactly the bad outcome I want to avoid.=C2=A0</div><div dir=3D"auto">=
<br></div><div dir=3D"auto">So if there really is a problem here, it would =
be good for you to make it clear. Your stated desire to preserve flexibilit=
y makes sense to me, but it doesn&#39;t contradict the reason already given=
 for <i>not </i>providing that flexibility.=C2=A0</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Is there some <i>other</i> reason why this is imp=
ortant to you, or is that it?</div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Sep 7, 2017 8:06 PM, &quot;Mark Andrews&quot; &l=
t;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br type=3D"=
attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br>
In message &lt;<a href=3D"mailto:BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue=
.com">BFAECDAF-8F4B-4C8D-AB7E-<wbr>1615BD54EF93@fugue.com</a>&gt;, Ted Lemo=
n writes:<br>
&gt;<br>
&gt; On Sep 7, 2017, at 12:59 AM, Mark Andrews &lt;<a href=3D"mailto:marka@=
isc.org">marka@isc.org</a>&gt; wrote:<br>
&gt; &gt; I shouldn&#39;t BE FORCED to hard code special LOCALHOST rules in=
to DNS<br>
&gt; &gt; tools.=C2=A0 Lookups should &quot;just work&quot; like they did b=
efore the root<br>
&gt; &gt; zone was signed.<br>
&gt;<br>
&gt; Because...?<br>
<br>
Because there are things you can do with localhost as a DNS zone<br>
that you can&#39;t do with /etc/hosts, NIS, etc. as they are limited<br>
to addresses only.<br>
<br>
Localhost should work just like home.arpa.=C2=A0 The tools we use shouldn&#=
39;t<br>
need special knowledge.=C2=A0 Special knowledge means EVERYTHING needs<br>
to be tested to see if it works with localhost as well and regular<br>
names.=C2=A0 That testing will get missed.=C2=A0 If it doesn&#39;t get miss=
ed it<br>
costs more money.=C2=A0 Workarounds for different behavior increases the<br=
>
probability of bugs being introduced as there will be seperate code<br>
paths.<br>
<br>
If I want to add a local trust anchor for localhost I will then<br>
need additional code to disable the workaround for the fact the<br>
root doesn&#39;t have a insecure delegation.<br>
<br>
Mark<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</blockquote></div></div>

--94eb2c05f4ca9dd1520558a42ee2--


From nobody Thu Sep  7 19:28:04 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7877C13309A for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 AvtgTYLRQaXB for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 19:27:59 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9026D13271E for <dnsop@ietf.org>; Thu,  7 Sep 2017 19:27:59 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 84C1924AE10; Fri,  8 Sep 2017 02:27:43 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 49A2B160045; Fri,  8 Sep 2017 02:27:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 2DBB8160046; Fri,  8 Sep 2017 02:27:50 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Bk5s9vGx_P1R; Fri,  8 Sep 2017 02:27:50 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A08C6160045; Fri,  8 Sep 2017 02:27:49 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C8F0D84A363E; Fri,  8 Sep 2017 12:27:47 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: dnsop WG <dnsop@ietf.org>, Warren Kumari <warren@kumari.net>, Tim Wicinski <tjw.ietf@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org> <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com> <20170908000559.DDBD7849CFAC@rock.dv.isc.org> <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
In-reply-to: Your message of "Thu, 07 Sep 2017 22:17:42 -0400." <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
Date: Fri, 08 Sep 2017 12:27:47 +1000
Message-Id: <20170908022747.C8F0D84A363E@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/doszRMqxOGEdJGndRM9vKqWFMkY>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 02:28:01 -0000

In message <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
, Ted Lemon writes:
> The discussion had covered the failure mode problem. There is substantial
> agreement that it's better for a stub that issues a query for localhost to
> fail than to succeed. You seem to disagree.

There are lots of people that don't want to deal with ICANN politics
and that is clouding their technical judgements.

> You haven't stated a reason for disagreeing—instead you've vigorously
> asserted that this is true. It's fine for you to do this, but if you were
> to get your way, that would be exactly the bad outcome I want to avoid.

So you want to break EVERY protocol that uses SRV to localhost.  I
stated clearly that there is stuff that you can do with DNS that
you can't do with /etc/hosts, NIS, etc.  One shouldn't have to
itemise everything that will be broken because full functionality
is not being provided.

> So if there really is a problem here, it would be good for you to make it
> clear. Your stated desire to preserve flexibility makes sense to me, but it
> doesn't contradict the reason already given for *not *providing that
> flexibility.
> 
> Is there some *other* reason why this is important to you, or is that it?
> 
> On Sep 7, 2017 8:06 PM, "Mark Andrews" <marka@isc.org> wrote:
> 
> >
> > In message <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>, Ted Lemon
> > writes:
> > >
> > > On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
> > > > I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
> > > > tools.  Lookups should "just work" like they did before the root
> > > > zone was signed.
> > >
> > > Because...?
> >
> > Because there are things you can do with localhost as a DNS zone
> > that you can't do with /etc/hosts, NIS, etc. as they are limited
> > to addresses only.
> >
> > Localhost should work just like home.arpa.  The tools we use shouldn't
> > need special knowledge.  Special knowledge means EVERYTHING needs
> > to be tested to see if it works with localhost as well and regular
> > names.  That testing will get missed.  If it doesn't get missed it
> > costs more money.  Workarounds for different behavior increases the
> > probability of bugs being introduced as there will be seperate code
> > paths.
> >
> > If I want to add a local trust anchor for localhost I will then
> > need additional code to disable the workaround for the fact the
> > root doesn't have a insecure delegation.
> >
> > Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
> 
> --94eb2c05f4ca9dd1520558a42ee2
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"auto">The discussion had covered the failure mode problem. Ther=
> e is substantial agreement that it&#39;s better for a stub that issues a qu=
> ery for localhost to fail than to succeed. You seem to disagree.<div dir=3D=
> "auto"><br></div><div dir=3D"auto">You haven&#39;t stated a reason for disa=
> greeing=E2=80=94instead you&#39;ve vigorously asserted that this is true. I=
> t&#39;s fine for you to do this, but if you were to get your way, that woul=
> d be exactly the bad outcome I want to avoid.=C2=A0</div><div dir=3D"auto">=
> <br></div><div dir=3D"auto">So if there really is a problem here, it would =
> be good for you to make it clear. Your stated desire to preserve flexibilit=
> y makes sense to me, but it doesn&#39;t contradict the reason already given=
>  for <i>not </i>providing that flexibility.=C2=A0</div><div dir=3D"auto"><b=
> r></div><div dir=3D"auto">Is there some <i>other</i> reason why this is imp=
> ortant to you, or is that it?</div></div><div class=3D"gmail_extra"><br><di=
> v class=3D"gmail_quote">On Sep 7, 2017 8:06 PM, &quot;Mark Andrews&quot; &l=
> t;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br type=3D"=
> attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
> order-left:1px #ccc solid;padding-left:1ex"><br>
> In message &lt;<a href=3D"mailto:BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue=
> .com">BFAECDAF-8F4B-4C8D-AB7E-<wbr>1615BD54EF93@fugue.com</a>&gt;, Ted Lemo=
> n writes:<br>
> &gt;<br>
> &gt; On Sep 7, 2017, at 12:59 AM, Mark Andrews &lt;<a href=3D"mailto:marka@=
> isc.org">marka@isc.org</a>&gt; wrote:<br>
> &gt; &gt; I shouldn&#39;t BE FORCED to hard code special LOCALHOST rules in=
> to DNS<br>
> &gt; &gt; tools.=C2=A0 Lookups should &quot;just work&quot; like they did b=
> efore the root<br>
> &gt; &gt; zone was signed.<br>
> &gt;<br>
> &gt; Because...?<br>
> <br>
> Because there are things you can do with localhost as a DNS zone<br>
> that you can&#39;t do with /etc/hosts, NIS, etc. as they are limited<br>
> to addresses only.<br>
> <br>
> Localhost should work just like home.arpa.=C2=A0 The tools we use shouldn&#=
> 39;t<br>
> need special knowledge.=C2=A0 Special knowledge means EVERYTHING needs<br>
> to be tested to see if it works with localhost as well and regular<br>
> names.=C2=A0 That testing will get missed.=C2=A0 If it doesn&#39;t get miss=
> ed it<br>
> costs more money.=C2=A0 Workarounds for different behavior increases the<br=
> >
> probability of bugs being introduced as there will be seperate code<br>
> paths.<br>
> <br>
> If I want to add a local trust anchor for localhost I will then<br>
> need additional code to disable the workaround for the fact the<br>
> root doesn&#39;t have a insecure delegation.<br>
> <br>
> Mark<br>
> --<br>
> Mark Andrews, ISC<br>
> 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
> PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
>  9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
> =A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
> </blockquote></div></div>
> 
> --94eb2c05f4ca9dd1520558a42ee2--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep  7 20:08:50 2017
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 976C91330AD for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 20:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 pOVhUF06KjIr for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 20:08:47 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B60D132F14 for <dnsop@ietf.org>; Thu,  7 Sep 2017 20:08:47 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id o200so4188085itg.0 for <dnsop@ietf.org>; Thu, 07 Sep 2017 20:08:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7t+kM8gvUPGe3VdNibqX2QtG5GgZSm7oXmN85KH5KTE=; b=MJbfYINKtLUCbxSmb9+3iwhiYGtyTEjZWbJypwPAr+aI+rIPIOHFuwVxiXRdgPaH8F yCUMT8BfMg/1JFAkQqn5kKELcCREhHJW8HqQu53QjLEHKYgN1wvnKRcxFdcMR7PQ2zBU BCeAbhtg5+tNq7/7iaKh55h4j5DOfd2DHart4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7t+kM8gvUPGe3VdNibqX2QtG5GgZSm7oXmN85KH5KTE=; b=IjdYebn7vK4ysquKqY5QwvToXhE+5wIiGlvnAPg8EGsLmeSTjHIluZRz64FCox/2c7 tYSt+KmKg87O3gYD7zY4ggHJ7Fgh/BhX0l3ONw9CipzrYWe5kAcwq5ek3iZO3EtVXsWv uWmv3wVD9a1JT642wq4KFUeEeyCXrw2pb8e3rryE/S6ilE7ObjoVjIUdJQRBYx+lOncR lTPxVtLpevjhyJAF+4dsYQbVFoTE7YhsI0zQ8s0mdSAJhz0e97env8extOgsziySg1zM 5mfJOyZrE2p79y7cBqJlXzs1XV6gp5UpfyYEsGFsfZqXpKSsqEZB5IPBxS/YOOcO0cQb 7hsg==
X-Gm-Message-State: AHPjjUiiR7kajAf2EaY4gJCIB7jQcXWOVB+V6CLOgq6fnCpl1cSqpDhn 1sfruMVUSaSJd8bI99vSUg==
X-Google-Smtp-Source: AOwi7QAWR/ZPM1+/vP/CIoOrwZDSRtu0R37jMHJyczidfcVAgMfbIf1FONG+YPdclm7j2nr8zQsC1Q==
X-Received: by 10.36.172.46 with SMTP id s46mr1325116ite.74.1504840125622; Thu, 07 Sep 2017 20:08:45 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:101:3:7998:3c45:d081:29ee? (node-131dv4p2g4zfv5kbu6.ipv6.teksavvy.com. [2607:f2c0:101:3:7998:3c45:d081:29ee]) by smtp.gmail.com with ESMTPSA id l197sm398040ita.2.2017.09.07.20.08.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Sep 2017 20:08:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (14G60)
In-Reply-To: <59B1F467.9010308@redbarn.org>
Date: Thu, 7 Sep 2017 23:08:43 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca>
References: <59B1F467.9010308@redbarn.org>
To: Paul Vixie <paul@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nhPnoQajgbx8R86ShWiP4_4e7sA>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 03:08:48 -0000

Apologies in advance for iPad MIME-crime. See below for crimes committed by w=
orkman rather than tools.

> On Sep 7, 2017, at 21:37, Paul Vixie <paul@redbarn.org> wrote:
>=20
> note, there's a proposal contained here.
>=20
> Jared Mauch wrote:
>>> On Thu, Sep 07, 2017 at 01:29:47PM -0700, Paul Vixie wrote:
>>> if the draft being considered was clear on two points, i'd support adopt=
ion.
>>>=20
>>> ...
>>=20
>>   Would you see the querying application informing you of intent via
>> option code saying "If I'm unable to talk to you once TTL expires, I may s=
erve
>> your last known good answer"?
>=20
> i don't think so. if it was "may i serve your last good answer?" then yes.=
 but with it as "i may" and the ? outside the quotes as shown above, then no=
.

There's a recursive operator with whom Jared and tale may be familiar that s=
ome time ago had a feature called "pinning" whereby particular names that we=
re known to be availability-sensitive (their non-availability caused great d=
isturbance in the helpdesk) could be "pinned" -- that is, in the recursive s=
erver, they were configured never to expire from the cache. They could be re=
freshed, but they would not expire.

When I remember learning about this I remember a certain personal conflict. T=
he goal in the implementation I referred to was edge-centric, in the sense t=
hat the goal was to reduce the opportunity for end-users to see breakage due=
 to DNS resolution failure. The recursive operator (and, by proxy, the acces=
s provider that was fielding the support calls) could probably find out in s=
hort order whether this was a safe thing to do for particular domains, and t=
hey chose the domains that should be pinned, but I thought and still think t=
hat that was a less desirable workflow than the zone manager signalling what=
 the behaviour should be in the event that authoritative servers couldn't be=
 reached. The implementation was pragmatically good, but I thought it could b=
e better.

The conversation I have seen so far is edge-centric; a recursive operator mi=
ght serve stale data because it believes that a stale answer is better than n=
o answer in all cases. A more granular approach might allow a recursive serv=
er to cache a record with multiple TTLs, indicating (for example) that ideal=
ly you would refresh this response after N seconds, but if you can't do that=
 then perhaps M seconds would be fine. A large M would reasonably approximat=
e "quite stale". Telling recursive servers what to do in the event of author=
ity servers being unreachable seems better as an authority server operator t=
han having to deal with a variety of behaviours between you and the end-user=
. This is different from a mechanism whereby a stub or downstream recursive r=
esolver would signal tolerance for stale data in responses.

This could be implemented maybe as an EDNS option used in the request and co=
rresponding response between a recursive server and an authority server. Que=
ries within zones that were not served by their authority servers configured=
 to supply the option or which were not requested by recursive servers prepa=
red to do the necessary would be handled conventionally.


Joe


From nobody Thu Sep  7 22:28:32 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19AD31330CC for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 22:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 zDDlYKCxz6l9 for <dnsop@ietfa.amsl.com>; Thu,  7 Sep 2017 22:28:31 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 379871330C8 for <dnsop@ietf.org>; Thu,  7 Sep 2017 22:28:31 -0700 (PDT)
Received: from localhost.localdomain (dhcp-182.access.lah1.vix.su [24.104.150.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id AC2A061FA2; Fri,  8 Sep 2017 05:28:30 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Joe Abley <jabley@hopcount.ca>
Cc: dnsop@ietf.org
Date: Thu, 07 Sep 2017 22:28:30 -0700
Message-ID: <8183111.Lxug4lBFgO@localhost.localdomain>
Organization: Vixie Freehold
User-Agent: KMail/4.13.0.25 (Linux/4.12.9-200.fc25.x86_64; KDE/4.14.30; x86_64; ; )
In-Reply-To: <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/u_qVgGjLXZNv2zZ0BpUxia-Scsg>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 05:28:32 -0000

On Thursday, September 07, 2017 11:08:43 PM Joe Abley wrote:
> >>   Would you see the querying application informing you of intent via
> >> 
> >> option code saying "If I'm unable to talk to you once TTL expires, I may
> >> serve your last known good answer"?
> > 
> > i don't think so. if it was "may i serve your last good answer?" then yes.
> > but with it as "i may" and the ? outside the quotes as shown above, then
> > no.
> There's a recursive operator with whom Jared and tale may be familiar that
> some time ago had a feature called "pinning" whereby particular names that
> were known to be availability-sensitive (their non-availability caused
> great disturbance in the helpdesk) could be "pinned" -- that is, in the
> recursive server, they were configured never to expire from the cache. They
> could be refreshed, but they would not expire.

the domain name system is the world's first and only distributed, coherent, 
autonomous, reliable database. if someone decides, for the sake of their help 
desk, to use my data for longer than the TTL i signaled, that's an affront to 
both coherence and autonomy, and they should stop.

if they really need this, they should provide a method by which i can specify 
both a TTL and an Expiry, and i will consider publishing both values, and if i 
do, then they can use them the way i intend them. because as i said, autonomy. 
it's my data, and my TTL.

vixie


From nobody Fri Sep  8 00:56:49 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDDFA1241F3 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 00:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 VsED1VUC6ENs for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 00:56:46 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3C04132D8C for <dnsop@ietf.org>; Fri,  8 Sep 2017 00:56:44 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id F1D292806C5; Fri,  8 Sep 2017 09:56:42 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id E34A62806C8; Fri,  8 Sep 2017 09:56:42 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id DB5FF2806C5; Fri,  8 Sep 2017 09:56:42 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id CDD0960286A3; Fri,  8 Sep 2017 09:56:42 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id C1345407E1; Fri,  8 Sep 2017 09:56:42 +0200 (CEST)
Date: Fri, 8 Sep 2017 09:56:42 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Joe Abley <jabley@hopcount.ca>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Message-ID: <20170908075642.latitn2ac66ptdr5@nic.fr>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B1CDAB08-6A2A-4D76-B3FB-0B267382930A@hopcount.ca>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.8.75116
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ztKuW95iIzYrlVcrlyIKknwSlm8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 07:56:48 -0000

On Thu, Sep 07, 2017 at 02:25:14PM -0400,
 Joe Abley <jabley@hopcount.ca> wrote 
 a message of 35 lines which said:

> However, the pragmatist in me says that people are already
> implementing things like this anyway, and a standard approach is
> better for all concerned than a fragmented set of
> uncomfortably-different implementations, which will surely make
> troubleshooting problems harder.

I'm not convinced by this reasoning. Either the opinion of the IETF
carries some weight with some actors, or it doesn't. In the first
case, we have to be careful of what we publish. In the second case, we
should close the shop immediately and go back playing video games,
since we are useless.

Also, in the specific case of draft-tale-dnsop-serve-stale, there is
another point: it is a local, unilateral decision by the resolver, not
_directly_ affecting interoperability. People can do strange things on
their resolvers (they already do). We should set rules (see first
paragraph) but, on resolver behavior, we have to be modest. So, I
don't think "a standard approach" is _mandatory_ in that specific
case.




From nobody Fri Sep  8 02:16:14 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 681C9132ECC for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 02:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.133
X-Spam-Level: 
X-Spam-Status: No, score=-4.133 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 qtRuHcWyJ72O for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 02:16:09 -0700 (PDT)
Received: from smtpbg65.qq.com (smtpbg65.qq.com [103.7.28.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7686132EC9 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:16:08 -0700 (PDT)
X-QQ-mid: bizesmtp14t1504862160tf9ilmse
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Fri, 08 Sep 2017 17:15:57 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: socDd1yRFi76+kEeYAHL7rOsA/D9KIU4hw8uZImomOYDEHfzdoQAX10+8/yst ZxTxZVIozgdBNg3LiXwc7KZvaIPAxuOYoX46l8n9Pm1iqkWbT5EGQROfbvyH32ScYDOcaeW wxZU+nEsmLAwALfb9+TfJJP4EflcZj6qTN5cn1IO6TptZJlQ7gcxWhS+WWNGE4dC0hCoHT+ 5QQ3+fWT9Ikg3d9ZXPbNfsWNzhbhVN/mLFp7+lKpkKkHcNX9O94702wyddX9vsOwUs5kQO0 1mEUHNgVaTn2oZkN/t5zPa9mCeKNP0AMhGPyVEpwOvBeR2aTJ276T3mYpX/c71UlPOYg==
X-QQ-GoodBg: 2
From: =?gb2312?B?RGF2ZXkgU29uZyjLzsHWvaEp?= <ljsong@biigroup.cn>
To: "'Stephane Bortzmeyer'" <bortzmeyer@nic.fr>, "'tjw ietf'" <tjw.ietf@gmail.com>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr>
In-Reply-To: <20170907154234.3z2zbju2sciiy7wr@nic.fr>
Date: Fri, 8 Sep 2017 17:15:56 +0800
Message-ID: <013a01d32883$163fc0a0$42bf41e0$@cn>+F7FF62F0D6181220
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdMn7/OD25BgqqnjSw6pJzFhe3TezgAklTBA
Content-Language: zh-cn
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xVVSDMr6aKrOgo-nqzswvIRjr0I>
Subject: [DNSOP] =?gb2312?b?tPC4tDogIEROU09QIENhbGwgZm9yIEFkb3B0aW9uIC0g?= =?gb2312?b?ZHJhZnQtdGFsZS1kbnNvcC1zZXJ2ZS1zdGFsZQ==?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 09:16:13 -0000

I just notice it asks for "Standards Track" document. If it aims to
introduce a special use of resolver to achieve some features for their
users' benefit, I think informational document may be more appropriate ? =
I
guess, like what RFC7706 does.=20

Davey

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: DNSOP [mailto:dnsop-bounces@ietf.org] =B4=FA=B1=ED =
Stephane Bortzmeyer
> =B7=A2=CB=CD=CA=B1=BC=E4: 2017=C4=EA9=D4=C27=C8=D5 23:43
> =CA=D5=BC=FE=C8=CB: tjw ietf
> =B3=AD=CB=CD: dnsop
> =D6=F7=CC=E2: Re: [DNSOP] DNSOP Call for Adoption - =
draft-tale-dnsop-serve-stale
>=20
> On Tue, Sep 05, 2017 at 03:25:39PM -0400,  tjw ietf =
<tjw.ietf@gmail.com>
> wrote  a message of 77 lines which said:
>=20
> > This starts a formal Call for Adoption for
> > draft-tale-dnsop-serve-stale
> >
> > The draft is available here:
> > https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
>=20
> I'm not enthousiastic. We should focus on making the DNS =
infrastructure
more
> reliable, not on adding something to a pile of already fragile =
protocols.
>=20
> There is also an opportunity that it masks failures and prevents =
people
from
> properly assigning blame: "example.com works if I use Something Public =
DNS
> but not if I use my ISP's resolver, therefore my ISP is broken".
>=20
> Also, the current draft does not make crystal-clear that stale data =
MUST
NOT
> be served unless no authoritative name server replies.
>=20
> If it is adopted, I think that requesting some way to convey the fact =
it
is stale to
> the client (Davey Song's message) is necessary.
>=20
> Regarding the draft, I'm surprised by the paragraph starting with =
"Paul
Vixie
> has suggested", paragraph which seems to completely ignore RFC 8020.
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop




From nobody Fri Sep  8 02:23:47 2017
Return-Path: <vladimir.cunat@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5CF132ECE for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 02:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 bju9KI6qpltB for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 02:23:43 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5D7C132EC9 for <dnsop@ietf.org>; Fri,  8 Sep 2017 02:23:43 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:4c57:feff:fe33:ef50] (unknown [IPv6:2001:1488:fffe:6:4c57:feff:fe33:ef50]) by mail.nic.cz (Postfix) with ESMTPSA id D5B92622F1; Fri,  8 Sep 2017 11:23:41 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1504862621; bh=IhoF7uXtIeYwE6Wh16PMg1grqA3lMXfi6SmmGjWKtLc=; h=To:From:Date; b=XnoEPYniSA69TNw+8crQxknU9axtOs1H98VfKvYwg6NpAprR6vRxkQ1bFqMRPWSt1 a5OD+s830/Fu+uSWcMpJWu06V7d2VcnXQVtDzX6qaJABQxxjTuiqHnhKv7Bp7r6LHL uRGq4t7RH2jH94He5B3KwjfLd7Vs2c0xVRqbGkok=
To: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
Cc: 'dnsop' <dnsop@ietf.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <013a01d32883$163fc0a0$42bf41e0$@cn>
From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?= <vladimir.cunat@nic.cz>
Message-ID: <a295ce8a-1ed2-9740-847d-3ba4d70bef4d@nic.cz>
Date: Fri, 8 Sep 2017 11:23:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <013a01d32883$163fc0a0$42bf41e0$@cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DgCJiWftrhZF86RH-CBXRcPa1kc>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiBETlNPUCBDYWxsIGZvciBBZG9wdGlvbiAt?= =?utf-8?q?_draft-tale-dnsop-serve-stale?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 09:23:45 -0000

On 09/08/2017 11:15 AM, Davey Song(宋林健) wrote:
> I just notice it asks for "Standards Track" document. If it aims to
> introduce a special use of resolver to achieve some features for their
> users' benefit, I think informational document may be more appropriate ? I
> guess, like what RFC7706 does. 

It was argued that the draft modifies the meaning of TTL and therefore
"updates" 1034+1035 which are on Standards Track.  I agree with that
point of view.

--Vladimir


From nobody Fri Sep  8 04:52:26 2017
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D328B13239C for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 04:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 qgCibGFvcmVE for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 04:52:22 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85EB81321AA for <dnsop@ietf.org>; Fri,  8 Sep 2017 04:52:22 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id d16so5200285ioj.3 for <dnsop@ietf.org>; Fri, 08 Sep 2017 04:52:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d59GgZ1wtD20Zb8I0LYZBELCUDvNC7rKLxlsjJz2+vc=; b=oekw8NfgrAgW1hBPCyhC8Tmm3XhsoWMyrTm6ID5MWJwvJYGI+FrF3Rt3fnKJotnUPL cJHPY3Gj4KNbjooCveKoSQg7yz7xwFB7QXDI2r+P6dPa16A8x6ZTmbCv5RgaGYcs/GVs yAxmol6mN4+OGHL6sNe/uwma4rzHtJCLmiSdw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d59GgZ1wtD20Zb8I0LYZBELCUDvNC7rKLxlsjJz2+vc=; b=jnkp21lU6BQkUtA7LJ2i7GLeVh1+rMbOAivFf4E+CjSC2T3xCGNYAfosZNbGhz/puG BMkQm3q5ewLCGGX4w1JyhY8rCbbg03aO1LrXFW8Hi4TU/uUtLuTGUSSYpayVEqTodOZc 5v2en0SfBFC1w7PJ/mtIJX3ik1t3CGNe/cAmpFWvaDLnVXtz7Jq+edvjz/5FByQZ65Uh 1d720LX0yDTJD3YffsDOgn4InzruzbJvSyNv5AcKe7OWjkcMYlLr6qK+DyqE5z15PaM1 KKqopIfOxfpIjmogGbF4My5NtWrq7MXLtVjig7JhQ/vWKlCoXUK+O4TL641B5we3tTLR 472Q==
X-Gm-Message-State: AHPjjUh+eU/o8tXEDu+OeIJqnbgUIqXqRUKgib7boPCaUteBFhUj+QtO tWwYR3IuzANhcu7YkRdXhA==
X-Google-Smtp-Source: AOwi7QDnFXrRz8JcjuyZAH/AnlNaJb2WSvUyAgrH1D7PddVoKmoEF7bcRjY+RQjZfY9juHaztqH8Gg==
X-Received: by 10.107.31.13 with SMTP id f13mr3332586iof.12.1504871541449; Fri, 08 Sep 2017 04:52:21 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:101:3:7998:3c45:d081:29ee? (node-131dv4p2g4zfv5kbu6.ipv6.teksavvy.com. [2607:f2c0:101:3:7998:3c45:d081:29ee]) by smtp.gmail.com with ESMTPSA id m123sm942539iom.25.2017.09.08.04.52.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Sep 2017 04:52:20 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (14G60)
In-Reply-To: <8183111.Lxug4lBFgO@localhost.localdomain>
Date: Fri, 8 Sep 2017 07:52:19 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <33D02832-2E7E-4C99-980E-E20FE0E34E5B@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain>
To: Paul Vixie <paul@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jNkJ1s9GAgfYdXOyJgXosbsmtYA>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 11:52:24 -0000

> On Sep 8, 2017, at 01:28, Paul Vixie <paul@redbarn.org> wrote:
>=20
> if they really need this, they should provide a method by which i can spec=
ify=20
> both a TTL and an Expiry, and i will consider publishing both values, and i=
f i=20
> do, then they can use them the way i intend them. because as i said, auton=
omy.=20
> it's my data, and my TTL.

Yes. That's a more succinct formulation of what I was trying to suggest.


Joe=


From nobody Fri Sep  8 05:07:39 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD6191321B6 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 05:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 J698UVI89M1J for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 05:07:32 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46CA81321AA for <dnsop@ietf.org>; Fri,  8 Sep 2017 05:07:31 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id d8so4545528pgt.4 for <dnsop@ietf.org>; Fri, 08 Sep 2017 05:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=40MzPbNa53NQfz9inCE+rxMj/HnOnT4VooVweL9hWZw=; b=REPC/MufO34Pno017WhDJvauqzk2NgViV9mCwKNvZ0paqBGNmoPAJM1DhmlbkBkQdg cNw3GWIO1wfUc5KGdGb8E0B/bzWx4pZ6zlggPgfU3vP5cOctZxJJI4ypyO/vmaZvlZof ubSSU0gD/ER5fUaZkSPPjTI4gYHHWiwgjSdS8UngodAkA0uLQyPyLYmnFYnBux2uAnBg o/d1NnjYvRRzchtFQ7YFwwjPdCPbw9pM4k3ON/WBekCuZpzOOMMb2k8PLOhakzilAjIj iPRmyEmH91mo/2gqoPb6R3HLeHqjJA0hn49GR83oerPddliWDVb3/1u7xOEYplvahHEg cF0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=40MzPbNa53NQfz9inCE+rxMj/HnOnT4VooVweL9hWZw=; b=Kmc8NviJdJjlVZQzNTYmN0r+dXYpTXOB9yX8nz1anVvgLDIjYdFFeT2QwR4F3BJSCD 9wBl+UK+ZxPCY1zgJ6MinTJi5rhnsPV4odHk32Ka24KdMEPd1CBGV2O93sp8PlZXPJtj i91oTMZ0bWEUfvFZRjzvfaS8ukTE3dF89Cp5EhWZ0sIeI+Jxtatk/f9MelzEl40lWeQK ANN8QAE2kbbNPDedFiymXfRQq+1e5kMfNfn48dte2IaBdmW8A0NVwCIDnlsAfZGZ0CAH e3nmYRE9PB5XT6qrzHAvpP9Kls2he0K+ioI2UiMKEJtEtCGHDm3MxlWBuEdw6I+z7xFs aH3g==
X-Gm-Message-State: AHPjjUi17dg3dOGDXLw1abrL/jVubJrA5POTTtEBetNjmGW7TnJWIpmf 6ufIjpzv45mfu6Yoccv+z53Son/PZkLX
X-Google-Smtp-Source: ADKCNb6L3FcHa3x1XxaV0Cxa4tFbpdeASo6Dk4nGW/N06Jw+9Ty6q8lrra3uP0ENEceee+qlYUeDX32cvDX6U83I764=
X-Received: by 10.98.150.151 with SMTP id s23mr2963531pfk.149.1504872451143; Fri, 08 Sep 2017 05:07:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.152.98 with HTTP; Fri, 8 Sep 2017 05:07:30 -0700 (PDT)
Received: by 10.100.152.98 with HTTP; Fri, 8 Sep 2017 05:07:30 -0700 (PDT)
In-Reply-To: <20170908022747.C8F0D84A363E@rock.dv.isc.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org> <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com> <20170908000559.DDBD7849CFAC@rock.dv.isc.org> <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com> <20170908022747.C8F0D84A363E@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 8 Sep 2017 08:07:30 -0400
Message-ID: <CAPt1N1nFs0G2huEaEszAXkYfVwJEhZ+uynRcCrR=zukjjh28Aw@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Warren Kumari <warren@kumari.net>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c0dfca6e212330558ac6ba2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EjPee_7xMjPoj3Tz4lbvutGPNuM>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 12:07:36 -0000

--94eb2c0dfca6e212330558ac6ba2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Do you know of protocols that use SRV to localhost in practice?

Anyway, this is like the question of whether to trust IP addresses when
using rsh. Remember rsh?  There's a reason we don't use it anymore, even
though it was definitely useful.

Localhost over DNS is analogous.

On Sep 7, 2017 10:28 PM, "Mark Andrews" <marka@isc.org> wrote:

>
> In message <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.
> gmail.com>
> , Ted Lemon writes:
> > The discussion had covered the failure mode problem. There is substanti=
al
> > agreement that it's better for a stub that issues a query for localhost
> to
> > fail than to succeed. You seem to disagree.
>
> There are lots of people that don't want to deal with ICANN politics
> and that is clouding their technical judgements.
>
> > You haven't stated a reason for disagreeing=E2=80=94instead you've vigo=
rously
> > asserted that this is true. It's fine for you to do this, but if you we=
re
> > to get your way, that would be exactly the bad outcome I want to avoid.
>
> So you want to break EVERY protocol that uses SRV to localhost.  I
> stated clearly that there is stuff that you can do with DNS that
> you can't do with /etc/hosts, NIS, etc.  One shouldn't have to
> itemise everything that will be broken because full functionality
> is not being provided.
>
> > So if there really is a problem here, it would be good for you to make =
it
> > clear. Your stated desire to preserve flexibility makes sense to me, bu=
t
> it
> > doesn't contradict the reason already given for *not *providing that
> > flexibility.
> >
> > Is there some *other* reason why this is important to you, or is that i=
t?
> >
> > On Sep 7, 2017 8:06 PM, "Mark Andrews" <marka@isc.org> wrote:
> >
> > >
> > > In message <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>, Ted Lemo=
n
> > > writes:
> > > >
> > > > On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
> > > > > I shouldn't BE FORCED to hard code special LOCALHOST rules into D=
NS
> > > > > tools.  Lookups should "just work" like they did before the root
> > > > > zone was signed.
> > > >
> > > > Because...?
> > >
> > > Because there are things you can do with localhost as a DNS zone
> > > that you can't do with /etc/hosts, NIS, etc. as they are limited
> > > to addresses only.
> > >
> > > Localhost should work just like home.arpa.  The tools we use shouldn'=
t
> > > need special knowledge.  Special knowledge means EVERYTHING needs
> > > to be tested to see if it works with localhost as well and regular
> > > names.  That testing will get missed.  If it doesn't get missed it
> > > costs more money.  Workarounds for different behavior increases the
> > > probability of bugs being introduced as there will be seperate code
> > > paths.
> > >
> > > If I want to add a local trust anchor for localhost I will then
> > > need additional code to disable the workaround for the fact the
> > > root doesn't have a insecure delegation.
> > >
> > > Mark
> > > --
> > > Mark Andrews, ISC
> > > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> > >
> >
> > --94eb2c05f4ca9dd1520558a42ee2
> > Content-Type: text/html; charset=3D"UTF-8"
> > Content-Transfer-Encoding: quoted-printable
> >
> > <div dir=3D3D"auto">The discussion had covered the failure mode problem=
.
> Ther=3D
> > e is substantial agreement that it&#39;s better for a stub that issues =
a
> qu=3D
> > ery for localhost to fail than to succeed. You seem to disagree.<div
> dir=3D3D=3D
> > "auto"><br></div><div dir=3D3D"auto">You haven&#39;t stated a reason fo=
r
> disa=3D
> > greeing=3DE2=3D80=3D94instead you&#39;ve vigorously asserted that this =
is
> true. I=3D
> > t&#39;s fine for you to do this, but if you were to get your way, that
> woul=3D
> > d be exactly the bad outcome I want to avoid.=3DC2=3DA0</div><div
> dir=3D3D"auto">=3D
> > <br></div><div dir=3D3D"auto">So if there really is a problem here, it
> would =3D
> > be good for you to make it clear. Your stated desire to preserve
> flexibilit=3D
> > y makes sense to me, but it doesn&#39;t contradict the reason already
> given=3D
> >  for <i>not </i>providing that flexibility.=3DC2=3DA0</div><div
> dir=3D3D"auto"><b=3D
> > r></div><div dir=3D3D"auto">Is there some <i>other</i> reason why this =
is
> imp=3D
> > ortant to you, or is that it?</div></div><div
> class=3D3D"gmail_extra"><br><di=3D
> > v class=3D3D"gmail_quote">On Sep 7, 2017 8:06 PM, &quot;Mark Andrews&qu=
ot;
> &l=3D
> > t;<a href=3D3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br
> type=3D3D"=3D
> > attribution"><blockquote class=3D3D"gmail_quote" style=3D3D"margin:0 0 =
0
> .8ex;b=3D
> > order-left:1px #ccc solid;padding-left:1ex"><br>
> > In message &lt;<a href=3D3D"mailto:BFAECDAF-8F4B-
> 4C8D-AB7E-1615BD54EF93@fugue=3D
> > .com">BFAECDAF-8F4B-4C8D-AB7E-<wbr>1615BD54EF93@fugue.com</a>&gt;, Ted
> Lemo=3D
> > n writes:<br>
> > &gt;<br>
> > &gt; On Sep 7, 2017, at 12:59 AM, Mark Andrews &lt;<a href=3D3D"mailto:
> marka@=3D
> > isc.org">marka@isc.org</a>&gt; wrote:<br>
> > &gt; &gt; I shouldn&#39;t BE FORCED to hard code special LOCALHOST rule=
s
> in=3D
> > to DNS<br>
> > &gt; &gt; tools.=3DC2=3DA0 Lookups should &quot;just work&quot; like th=
ey
> did b=3D
> > efore the root<br>
> > &gt; &gt; zone was signed.<br>
> > &gt;<br>
> > &gt; Because...?<br>
> > <br>
> > Because there are things you can do with localhost as a DNS zone<br>
> > that you can&#39;t do with /etc/hosts, NIS, etc. as they are limited<br=
>
> > to addresses only.<br>
> > <br>
> > Localhost should work just like home.arpa.=3DC2=3DA0 The tools we use
> shouldn&#=3D
> > 39;t<br>
> > need special knowledge.=3DC2=3DA0 Special knowledge means EVERYTHING
> needs<br>
> > to be tested to see if it works with localhost as well and regular<br>
> > names.=3DC2=3DA0 That testing will get missed.=3DC2=3DA0 If it doesn&#3=
9;t get
> miss=3D
> > ed it<br>
> > costs more money.=3DC2=3DA0 Workarounds for different behavior increase=
s
> the<br=3D
> > >
> > probability of bugs being introduced as there will be seperate code<br>
> > paths.<br>
> > <br>
> > If I want to add a local trust anchor for localhost I will then<br>
> > need additional code to disable the workaround for the fact the<br>
> > root doesn&#39;t have a insecure delegation.<br>
> > <br>
> > Mark<br>
> > --<br>
> > Mark Andrews, ISC<br>
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
> > PHONE: <a href=3D3D"tel:%2B61%202%209871%204742"
> value=3D3D"+61298714742">+61 2=3D
> >  9871 4742</a>=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =
=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0
> =3DC2=3D
> > =3DA0INTERNET: <a href=3D3D"mailto:marka@isc.org">marka@isc.org</a><br>
> > </blockquote></div></div>
> >
> > --94eb2c05f4ca9dd1520558a42ee2--
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

--94eb2c0dfca6e212330558ac6ba2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Do you know of protocols that use SRV to localhost in pra=
ctice?<div dir=3D"auto"><br></div><div dir=3D"auto">Anyway, this is like th=
e question of whether to trust IP addresses when using rsh. Remember rsh?=
=C2=A0 There&#39;s a reason we don&#39;t use it anymore, even though it was=
 definitely useful.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Loca=
lhost over DNS is analogous.=C2=A0</div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Sep 7, 2017 10:28 PM, &quot;Mark Andrews&qu=
ot; &lt;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
In message &lt;<a href=3D"mailto:CAPt1N1kKNRU%2BmF-JVti_CKS25%2B7g5BFH8Yko5=
3-VKgZqVreZuQ@mail.gmail.com">CAPt1N1kKNRU+mF-JVti_CKS25+<wbr>7g5BFH8Yko53-=
VKgZqVreZuQ@mail.<wbr>gmail.com</a>&gt;<br>
, Ted Lemon writes:<br>
&gt; The discussion had covered the failure mode problem. There is substant=
ial<br>
&gt; agreement that it&#39;s better for a stub that issues a query for loca=
lhost to<br>
&gt; fail than to succeed. You seem to disagree.<br>
<br>
There are lots of people that don&#39;t want to deal with ICANN politics<br=
>
and that is clouding their technical judgements.<br>
<br>
&gt; You haven&#39;t stated a reason for disagreeing=E2=80=94instead you&#3=
9;ve vigorously<br>
&gt; asserted that this is true. It&#39;s fine for you to do this, but if y=
ou were<br>
&gt; to get your way, that would be exactly the bad outcome I want to avoid=
.<br>
<br>
So you want to break EVERY protocol that uses SRV to localhost.=C2=A0 I<br>
stated clearly that there is stuff that you can do with DNS that<br>
you can&#39;t do with /etc/hosts, NIS, etc.=C2=A0 One shouldn&#39;t have to=
<br>
itemise everything that will be broken because full functionality<br>
is not being provided.<br>
<br>
&gt; So if there really is a problem here, it would be good for you to make=
 it<br>
&gt; clear. Your stated desire to preserve flexibility makes sense to me, b=
ut it<br>
&gt; doesn&#39;t contradict the reason already given for *not *providing th=
at<br>
&gt; flexibility.<br>
&gt;<br>
&gt; Is there some *other* reason why this is important to you, or is that =
it?<br>
&gt;<br>
&gt; On Sep 7, 2017 8:06 PM, &quot;Mark Andrews&quot; &lt;<a href=3D"mailto=
:marka@isc.org">marka@isc.org</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; In message &lt;<a href=3D"mailto:BFAECDAF-8F4B-4C8D-AB7E-1615BD54=
EF93@fugue.com">BFAECDAF-8F4B-4C8D-AB7E-<wbr>1615BD54EF93@fugue.com</a>&gt;=
, Ted Lemon<br>
&gt; &gt; writes:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Sep 7, 2017, at 12:59 AM, Mark Andrews &lt;<a href=3D"mai=
lto:marka@isc.org">marka@isc.org</a>&gt; wrote:<br>
&gt; &gt; &gt; &gt; I shouldn&#39;t BE FORCED to hard code special LOCALHOS=
T rules into DNS<br>
&gt; &gt; &gt; &gt; tools.=C2=A0 Lookups should &quot;just work&quot; like =
they did before the root<br>
&gt; &gt; &gt; &gt; zone was signed.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Because...?<br>
&gt; &gt;<br>
&gt; &gt; Because there are things you can do with localhost as a DNS zone<=
br>
&gt; &gt; that you can&#39;t do with /etc/hosts, NIS, etc. as they are limi=
ted<br>
&gt; &gt; to addresses only.<br>
&gt; &gt;<br>
&gt; &gt; Localhost should work just like home.arpa.=C2=A0 The tools we use=
 shouldn&#39;t<br>
&gt; &gt; need special knowledge.=C2=A0 Special knowledge means EVERYTHING =
needs<br>
&gt; &gt; to be tested to see if it works with localhost as well and regula=
r<br>
&gt; &gt; names.=C2=A0 That testing will get missed.=C2=A0 If it doesn&#39;=
t get missed it<br>
&gt; &gt; costs more money.=C2=A0 Workarounds for different behavior increa=
ses the<br>
&gt; &gt; probability of bugs being introduced as there will be seperate co=
de<br>
&gt; &gt; paths.<br>
&gt; &gt;<br>
&gt; &gt; If I want to add a local trust anchor for localhost I will then<b=
r>
&gt; &gt; need additional code to disable the workaround for the fact the<b=
r>
&gt; &gt; root doesn&#39;t have a insecure delegation.<br>
&gt; &gt;<br>
&gt; &gt; Mark<br>
&gt; &gt; --<br>
&gt; &gt; Mark Andrews, ISC<br>
&gt; &gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
&gt; &gt; PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714=
742">+61 2 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><b=
r>
&gt; &gt;<br>
&gt;<br>
&gt; --94eb2c05f4ca9dd1520558a42ee2<br>
&gt; Content-Type: text/html; charset=3D&quot;UTF-8&quot;<br>
&gt; Content-Transfer-Encoding: quoted-printable<br>
&gt;<br>
&gt; &lt;div dir=3D3D&quot;auto&quot;&gt;The discussion had covered the fai=
lure mode problem. Ther=3D<br>
&gt; e is substantial agreement that it&amp;#39;s better for a stub that is=
sues a qu=3D<br>
&gt; ery for localhost to fail than to succeed. You seem to disagree.&lt;di=
v dir=3D3D=3D<br>
&gt; &quot;auto&quot;&gt;&lt;br&gt;&lt;/div&gt;&lt;div dir=3D3D&quot;auto&q=
uot;&gt;You haven&amp;#39;t stated a reason for disa=3D<br>
&gt; greeing=3DE2=3D80=3D94instead you&amp;#39;ve vigorously asserted that =
this is true. I=3D<br>
&gt; t&amp;#39;s fine for you to do this, but if you were to get your way, =
that woul=3D<br>
&gt; d be exactly the bad outcome I want to avoid.=3DC2=3DA0&lt;/div&gt;&lt=
;div dir=3D3D&quot;auto&quot;&gt;=3D<br>
&gt; &lt;br&gt;&lt;/div&gt;&lt;div dir=3D3D&quot;auto&quot;&gt;So if there =
really is a problem here, it would =3D<br>
&gt; be good for you to make it clear. Your stated desire to preserve flexi=
bilit=3D<br>
&gt; y makes sense to me, but it doesn&amp;#39;t contradict the reason alre=
ady given=3D<br>
&gt;=C2=A0 for &lt;i&gt;not &lt;/i&gt;providing that flexibility.=3DC2=3DA0=
&lt;/div&gt;&lt;div dir=3D3D&quot;auto&quot;&gt;&lt;b=3D<br>
&gt; r&gt;&lt;/div&gt;&lt;div dir=3D3D&quot;auto&quot;&gt;Is there some &lt=
;i&gt;other&lt;/i&gt; reason why this is imp=3D<br>
&gt; ortant to you, or is that it?&lt;/div&gt;&lt;/div&gt;&lt;div class=3D3=
D&quot;gmail_extra&quot;&gt;&lt;br&gt;&lt;di=3D<br>
&gt; v class=3D3D&quot;gmail_quote&quot;&gt;On Sep 7, 2017 8:06 PM, &amp;qu=
ot;Mark Andrews&amp;quot; &amp;l=3D<br>
&gt; t;&lt;a href=3D3D&quot;mailto:<a href=3D"mailto:marka@isc.org">marka@i=
sc.org</a>&quot;&gt;<a href=3D"mailto:marka@isc.org"><wbr>marka@isc.org</a>=
&lt;/a&gt;&amp;gt; wrote:&lt;br type=3D3D&quot;=3D<br>
&gt; attribution&quot;&gt;&lt;blockquote class=3D3D&quot;gmail_quote&quot; =
style=3D3D&quot;margin:0 0 0 .8ex;b=3D<br>
&gt; order-left:1px #ccc solid;padding-left:1ex&quot;&gt;&lt;br&gt;<br>
&gt; In message &amp;lt;&lt;a href=3D3D&quot;mailto:<a href=3D"mailto:BFAEC=
DAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue">BFAECDAF-8F4B-<wbr>4C8D-AB7E-1615BD5=
4EF93@fugue</a>=3D<br>
&gt; .com&quot;&gt;BFAECDAF-8F4B-4C8D-AB7E-<wbr>&lt;wbr&gt;<a href=3D"mailt=
o:1615BD54EF93@fugue.com">1615BD54EF93@fugue.com</a>&lt;/<wbr>a&gt;&amp;gt;=
, Ted Lemo=3D<br>
&gt; n writes:&lt;br&gt;<br>
&gt; &amp;gt;&lt;br&gt;<br>
&gt; &amp;gt; On Sep 7, 2017, at 12:59 AM, Mark Andrews &amp;lt;&lt;a href=
=3D3D&quot;mailto:<a href=3D"mailto:marka@">marka@</a>=3D<br>
&gt; <a href=3D"http://isc.org" rel=3D"noreferrer" target=3D"_blank">isc.or=
g</a>&quot;&gt;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&lt;/a&gt;=
&amp;gt; wrote:&lt;br&gt;<br>
&gt; &amp;gt; &amp;gt; I shouldn&amp;#39;t BE FORCED to hard code special L=
OCALHOST rules in=3D<br>
&gt; to DNS&lt;br&gt;<br>
&gt; &amp;gt; &amp;gt; tools.=3DC2=3DA0 Lookups should &amp;quot;just work&=
amp;quot; like they did b=3D<br>
&gt; efore the root&lt;br&gt;<br>
&gt; &amp;gt; &amp;gt; zone was signed.&lt;br&gt;<br>
&gt; &amp;gt;&lt;br&gt;<br>
&gt; &amp;gt; Because...?&lt;br&gt;<br>
&gt; &lt;br&gt;<br>
&gt; Because there are things you can do with localhost as a DNS zone&lt;br=
&gt;<br>
&gt; that you can&amp;#39;t do with /etc/hosts, NIS, etc. as they are limit=
ed&lt;br&gt;<br>
&gt; to addresses only.&lt;br&gt;<br>
&gt; &lt;br&gt;<br>
&gt; Localhost should work just like home.arpa.=3DC2=3DA0 The tools we use =
shouldn&amp;#=3D<br>
&gt; 39;t&lt;br&gt;<br>
&gt; need special knowledge.=3DC2=3DA0 Special knowledge means EVERYTHING n=
eeds&lt;br&gt;<br>
&gt; to be tested to see if it works with localhost as well and regular&lt;=
br&gt;<br>
&gt; names.=3DC2=3DA0 That testing will get missed.=3DC2=3DA0 If it doesn&a=
mp;#39;t get miss=3D<br>
&gt; ed it&lt;br&gt;<br>
&gt; costs more money.=3DC2=3DA0 Workarounds for different behavior increas=
es the&lt;br=3D<br>
&gt; &gt;<br>
&gt; probability of bugs being introduced as there will be seperate code&lt=
;br&gt;<br>
&gt; paths.&lt;br&gt;<br>
&gt; &lt;br&gt;<br>
&gt; If I want to add a local trust anchor for localhost I will then&lt;br&=
gt;<br>
&gt; need additional code to disable the workaround for the fact the&lt;br&=
gt;<br>
&gt; root doesn&amp;#39;t have a insecure delegation.&lt;br&gt;<br>
&gt; &lt;br&gt;<br>
&gt; Mark&lt;br&gt;<br>
&gt; --&lt;br&gt;<br>
&gt; Mark Andrews, ISC&lt;br&gt;<br>
&gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia&lt;br&gt;<br>
&gt; PHONE: &lt;a href=3D3D&quot;tel:%2B61%202%209871%<wbr>204742&quot; val=
ue=3D3D&quot;+61298714742&quot;&gt;+61 2=3D<br>
&gt;=C2=A0 9871 4742&lt;/a&gt;=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =
=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3D<br>
&gt; =3DA0INTERNET: &lt;a href=3D3D&quot;mailto:<a href=3D"mailto:marka@isc=
.org">marka@isc.org</a>&quot;&gt;<a href=3D"mailto:marka@isc.org"><wbr>mark=
a@isc.org</a>&lt;/a&gt;&lt;br&gt;<br>
&gt; &lt;/blockquote&gt;&lt;/div&gt;&lt;/div&gt;<br>
&gt;<br>
&gt; --<wbr>94eb2c05f4ca9dd1520558a42ee2--<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: +61 2 9871 4742=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</blockquote></div></div>

--94eb2c0dfca6e212330558ac6ba2--


From nobody Fri Sep  8 07:16:58 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A0313291C for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 U_PvTwtAh163 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:16:54 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4083132153 for <dnsop@ietf.org>; Fri,  8 Sep 2017 07:16:54 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:41566) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dqK5U-00006o-0d (Exim 4.89) (return-path <dot@dotat.at>); Fri, 08 Sep 2017 15:16:52 +0100
Date: Fri, 8 Sep 2017 15:16:52 +0100
From: Tony Finch <dot@dotat.at>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
cc: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
In-Reply-To: <20170907154234.3z2zbju2sciiy7wr@nic.fr>
Message-ID: <alpine.DEB.2.11.1709081459550.2676@grey.csi.cam.ac.uk>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r6gIQxUUmQAhib1il11HFZXXzUM>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 14:16:57 -0000

Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>
> I'm not enthousiastic. We should focus on making the DNS infrastructure
> more reliable, not on adding something to a pile of already fragile
> protocols.

I like this draft because it should help if we lose off-campus
connectivity. We've had a few incidents in recent years such as flooded
comms rooms and DDoS attacks on our providers. Those problems have been
addressed at the network layer, but if we have another outage for whatever
reason I would like our recursive servers to be able to handle it more
gracefully.

We have set things up so it should be possible to resolve on-site names in
our own domains when there is an outage - but not if the client does
DNSSEC validation. It isn't possible to distribute trust anchors to BYOD
clients with validating stubs, so the only way to keep going through an
outage is to retain the DS/DNSKEY chain in the cache.

It's also mildly annoying that loss of connectivity often looks like a DNS
problem, since client software never gets as far as trying to connect off
site. I would selfishly prefer it if our users would blame the network
rather than the DNS :-)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Shannon: Northwest 5 to 7, occasionally gale 8 later. Rough or very rough.
Showers. Good.


From nobody Fri Sep  8 07:32:42 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1731132EE6 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 MzvUwEpaTrK5 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:32:35 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8D99132D79 for <dnsop@ietf.org>; Fri,  8 Sep 2017 07:32:35 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:41938) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dqKKf-000JKR-00 (Exim 4.89) (return-path <dot@dotat.at>); Fri, 08 Sep 2017 15:32:33 +0100
Date: Fri, 8 Sep 2017 15:32:32 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Vixie <paul@redbarn.org>
cc: Joe Abley <jabley@hopcount.ca>, dnsop@ietf.org
In-Reply-To: <8183111.Lxug4lBFgO@localhost.localdomain>
Message-ID: <alpine.DEB.2.11.1709081524290.2676@grey.csi.cam.ac.uk>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-JRQ-KxRbuqic9mhyNW8VUeIUBo>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 14:32:42 -0000

Paul Vixie <paul@redbarn.org> wrote:
>
> if they really need this, they should provide a method by which i can specify
> both a TTL and an Expiry, and i will consider publishing both values, and if i
> do, then they can use them the way i intend them.

RRSIG sort-of does that?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Sole, Lundy, Fastnet: West veering northwest 5 to 7. Rough in Sole, otherwise
moderate or rough, occasionally very rough later in Sole and southwest
Fastnet. Thundery showers. Good, occasionally moderate.


From nobody Fri Sep  8 07:59:19 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52FA313292E for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 bkR5_80FzDuD for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 07:59:16 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F82132925 for <dnsop@ietf.org>; Fri,  8 Sep 2017 07:59:16 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:7d2f:c94b:ef87:a849] (unknown [IPv6:2001:559:8000:c9:7d2f:c94b:ef87:a849]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id EBF2661FA2; Fri,  8 Sep 2017 14:59:15 +0000 (UTC)
Message-ID: <59B2B042.7000109@redbarn.org>
Date: Fri, 08 Sep 2017 07:59:14 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: Joe Abley <jabley@hopcount.ca>, dnsop@ietf.org
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <alpine.DEB.2.11.1709081524290.2676@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1709081524290.2676@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/G7a3o_ktAzttfpgLvxMAuV2lpsU>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 14:59:17 -0000

Tony Finch wrote:
> Paul Vixie<paul@redbarn.org>  wrote:
>> if they really need this, they should provide a method by which i can specify
>> both a TTL and an Expiry, and i will consider publishing both values, and if i
>> do, then they can use them the way i intend them.
>
> RRSIG sort-of does that?

but it wasn't intended as that, so my use of it cannot be interpreted as 
permission to treat it as that.

-- 
P Vixie


From nobody Fri Sep  8 09:57:17 2017
Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6E3132D18 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 09:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 AiGuJPoQqXVC for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 09:57:13 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B92E132D42 for <dnsop@ietf.org>; Fri,  8 Sep 2017 09:57:13 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3xpk523s2VzFTQ; Fri,  8 Sep 2017 18:57:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1504889830; bh=tU7s/AmjciZw3G9Yi+/6affUv2Hhsp9ziLL8BqITjpg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Gp3pfsC3hZ1G/ubfYo2ff9aVXiacl4sSoSiiFI742VLytReZFeNLzijpzzHduiu+H f5jPgFi+jcOY0CQ8ykpTkTqa5MMp/hVgcO0mJcO4I1J/1GjS8jx04DzehTT94M6nL/ tQJg2SFQTq3ewTYEskvNvEAQnVep2Xqgj5mqJ/bU=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id dCTApUJKPguE; Fri,  8 Sep 2017 18:57:06 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri,  8 Sep 2017 18:57:06 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id BF2A7378B47; Fri,  8 Sep 2017 12:57:05 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca BF2A7378B47
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id AA4464129B5A; Fri,  8 Sep 2017 12:57:05 -0400 (EDT)
Date: Fri, 8 Sep 2017 12:57:05 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Tony Finch <dot@dotat.at>
cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, tjw ietf <tjw.ietf@gmail.com>,  dnsop <dnsop@ietf.org>
In-Reply-To: <alpine.DEB.2.11.1709081459550.2676@grey.csi.cam.ac.uk>
Message-ID: <alpine.LRH.2.21.1709081255090.16539@bofh.nohats.ca>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <alpine.DEB.2.11.1709081459550.2676@grey.csi.cam.ac.uk>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4gvQYR0nKnZsGVNigBBHxZ4isZ8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 16:57:16 -0000

On Fri, 8 Sep 2017, Tony Finch wrote:

> It isn't possible to distribute trust anchors to BYOD
> clients with validating stubs

That's not entirely true,

https://tools.ietf.org/html/draft-ietf-ipsecme-split-dns-02

It supports sending INTERNAL_DNSSEC_TA trust anchors.

Paul


From nobody Fri Sep  8 10:11:30 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D452E124B18 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 10:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 VaQZl9MwbK-R for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 10:11:27 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74BA813219F for <dnsop@ietf.org>; Fri,  8 Sep 2017 10:11:27 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:45911) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dqMoO-000AQU-2E (Exim 4.89) (return-path <dot@dotat.at>); Fri, 08 Sep 2017 18:11:24 +0100
Date: Fri, 8 Sep 2017 18:11:24 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Wouters <paul@nohats.ca>
cc: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
In-Reply-To: <alpine.LRH.2.21.1709081255090.16539@bofh.nohats.ca>
Message-ID: <alpine.DEB.2.11.1709081809250.2676@grey.csi.cam.ac.uk>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <alpine.DEB.2.11.1709081459550.2676@grey.csi.cam.ac.uk> <alpine.LRH.2.21.1709081255090.16539@bofh.nohats.ca>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gs9L3fdL77Gu6ghEOgqTXJoWsoo>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 17:11:29 -0000

Paul Wouters <paul@nohats.ca> wrote:
> On Fri, 8 Sep 2017, Tony Finch wrote:
>
> > It isn't possible to distribute trust anchors to BYOD
> > clients with validating stubs
>
> That's not entirely true,
> https://tools.ietf.org/html/draft-ietf-ipsecme-split-dns-02
> It supports sending INTERNAL_DNSSEC_TA trust anchors.

Nice!

But I'm not sure it's entirely sensible to depend on a VPN to make an
on-campus connection work properly :-)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Rockall: Northwest 6 to gale 8, decreasing 4 or 5 later. Rough or very rough.
Rain or showers. Moderate or good.


From nobody Fri Sep  8 12:53:20 2017
Return-Path: <edmonds@mycre.ws>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4DA124205 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 12:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 XL7H-KERpoc0 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 12:53:17 -0700 (PDT)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B9D01204DA for <dnsop@ietf.org>; Fri,  8 Sep 2017 12:53:17 -0700 (PDT)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 7B18212C0F9E; Fri,  8 Sep 2017 15:53:16 -0400 (EDT)
Date: Fri, 8 Sep 2017 15:53:16 -0400
From: Robert Edmonds <edmonds@mycre.ws>
To: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Message-ID: <20170908195316.ncphh3ru5v7f233g@mycre.ws>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4escQnq7BvdikIJz0rrXCf5zDkc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 19:53:19 -0000

tjw ietf wrote:
> August is over and my self-imposed holiday is over, so it's time to get
> busy again. We have this document marked as a candidate for adoption.
> 
> This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale
> 
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
> 
> Please review this draft to see if you think it is suitable for adoption by
> DNSOP, and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.
> 
> *If You have already stated your position for or against adoption, we are
> counting those so you do not need to repeat yourself. *
> 
> This call for adoption ends: 19 September 2017
> 
> Thanks,
> tim wicinski
> DNSOP co-chair

Hi,

I support the adoption of this document.

Comments:

This document is marked as updating 1034 and 1035 but it's not clear
what text from those documents is being updated. E.g. compare to
"NXDOMAIN: There Really Is Nothing Underneath" (RFC 8020) which
explicitly documents its revisions in its Section 3.

I think the claim in the introduction, "Notably, the original DNS
specification does not say that data past its expiration cannot be used"
should either be justified further or removed. The "should again be
consulted" text from STD 13 could be read in isolation as permitting
serve stale, but it's the weakest text out of these three TTL
definitions given in STD 13:

RFC 1034 §3.6:

    "The TTL describes how long a RR can be cached before it should be
    discarded. […] The meaning of the TTL field is a time limit on how
    long an RR can be kept in a cache."

RFC 1035 §3.2.1:

    "a 32 bit […] integer that specifies the time interval that the
    resource record may be cached before the source of the information
    should again be consulted."

RFC 1035 §4.1.3:

    "a 32 bit […] integer that specifies the time interval (in seconds)
    that the resource record may be cached before it should be
    discarded."

That is, if "the original DNS specification does not say that data past
its expiration cannot be used" is true, then this document doesn't need
to update STD 13, and maybe it should only be an informational document.
But if it's not true (and I don't think it is, based on the other two
TTL definitions in STD 13), then a new TTL definition should be given
that permits the serve stale mechanism.

Also, just for fun, this text from RFC 882 exists (p.28 "Resolvers with
cache management") and is even stronger than the text in STD 13:

    "When a resolver caches a returned resource record it must also
    remember the TTL field.  The resolver must discard the record when
    the equivalent amount of time has passed."

-- 
Robert Edmonds


From nobody Fri Sep  8 13:11:32 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4367132811 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 13:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nP1IMKFdicAB for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 13:11:29 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551BA1321E6 for <dnsop@ietf.org>; Fri,  8 Sep 2017 13:11:29 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id i50so9114757qtf.0 for <dnsop@ietf.org>; Fri, 08 Sep 2017 13:11:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=/c0Xx6IPqHumFEfcfs8eWML1KFwp5AJMOWe9WiwctdI=; b=ksZtX+FFmmmHoBNarDxekZcYsMPa5P9ck9yVTWHTOraqW/AG5HayvgZBAxGGKOoVZ3 T3WrUIZxQ6v6WALpIoN7LmipZlE/7B09CiFgAm/Jq3cOeogk2veNHxOLLQjQ2+CbAPEz jfNQr7sVxI43N8PaxNIJDYw1Ekz+5Hgog9SEi/U6kM8d3DhGxBiHBWuuYcN/mYBaiJGj fMQmZU17C2x1AE+W3F+k9ewaQanoQHDyYozeFh3U0fNXI46ZXRBNMXBA3ijZGcdAjJXu 9mR8FLZr9BetHpJ3SrhIejuC9Y++GnyzV9Y+8I5PjlPbsmgaBBIRZPliYaaPy9RQyrxV 0NvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=/c0Xx6IPqHumFEfcfs8eWML1KFwp5AJMOWe9WiwctdI=; b=kaec5wS8S8K09taTXJCRO82PEFmau0n9RvKuaaCigZKqYcAYeF1eeV8kx6nBUQxj27 GgQr6w+lxYjOoJZHKiLaRS/zTmMjRNFM705toHZGmdnuXvkmLvv3ngqC0yMT3mJ5en6d WrFr40gNvs2WuhA0a/Vd/fKH8q6ekKMg+RlbYtouJxpG46SfKroyXmQIwdZXS4DbqSv/ cIlrOrUMP9ZvKMfBtDCuwdpRikqNqAtDlrAG/d0lxZtApaJgwipF3KVzgC6GsxM6uBRW inQA7jJueE+cA3eg83ucsv73xXtmEa3jc2oNXmXsxjmJoTk9WGvPJUbbuYp4k/3O0Wiy 1BBQ==
X-Gm-Message-State: AHPjjUhytN1jH2EiiU9T3J7hkkAsVwJi+ghhEX/0sjdx4aoj8/br50nE ERuDWiZKXkHpeYCWMLkhBXYYA55+XHHuPwM=
X-Google-Smtp-Source: AOwi7QDUjmxQ6OnInnj2R+MWoTs46p9AxVHwdAa4PaCnj7BU7qSY65f5miBvtxO9GP/zBx3iV316QfKxSTZsj1/SCEM=
X-Received: by 10.200.49.232 with SMTP id i37mr6108520qte.281.1504901488339; Fri, 08 Sep 2017 13:11:28 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.200.54.104 with HTTP; Fri, 8 Sep 2017 13:11:27 -0700 (PDT)
In-Reply-To: <8826934.gJBl6qSRLR@localhost.localdomain>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <ybltw0emmvh.fsf@wu.hardakers.net> <CAJE_bqc9zD3Um2oWri7K3L10=MWrUrKpCHpmUGAADKUmFmPYCg@mail.gmail.com> <8826934.gJBl6qSRLR@localhost.localdomain>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Fri, 8 Sep 2017 13:11:27 -0700
X-Google-Sender-Auth: 2KakQipTbgMKBcQfYtmKodczEz8
Message-ID: <CAJE_bqeDdtgsC7pZ8TcxufuimbLBU0t+xJKV1VL+OJui8G9wLw@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/F0Jd8pBoCIIm9FNv5gXpgdmQEw4>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 20:11:31 -0000

At Thu, 07 Sep 2017 13:42:45 -0700,
Paul Vixie <paul@redbarn.org> wrote:

> > If we don't work on a proposal like this, I'd love to see a specific
> > counter proposal that doesn't violate the current protocol
> > specification (i.e., using a cached answer beyond its TTL) and still
> > avoids resolution failure when authoritative servers are forced to be
> > non-responsive due to huge scale DoS attacks.
>
> i think the actual problem statement is broader, and that by solving for this
> narrow version, we would lose the complexity/capability tradeoff -- we'd add
> more state and more signaling at a cost higher than what we would get for it.

I'm not sure specifically what you mean by these, but...

> it's a general reachability problem not specifically ddos problem. reasons for
> not being able to refresh data in a cache include ddos, but also backhoes,
> wire cutters, squirrels, circuit breakers, and bad design/provisioning.

...I agree here.  I'm well aware of the generic nature of the issue,
but I mentioned one specific instance of the problem in my previous
message just because that's the most obvious one.

> i think the right answer will look like a miniature version of IXFR/AXFR and
> NOTIFY, such that a cache can register its intent to become a partial stealth
> secondary server, and by participating, an authority server can both indicate
> its willingness to have this done, and possibly remember what was transmitted
> so as to facilitate subsequent cache invalidation or zone change notification
> messaging. one could even imagine a dns cookie exchange at the outset, to help
> authenticate later messages. sort of a super-lightweight session protocol.

I guess we are also on the same page in a sense here.  One possible
justification for a behavior like draft-tale-dnsop-serve-stale is that
it can be considered a recursive server variant of a secondary
authoritative server that keeps using primary's zone content even if
the auth server is unreachable for a certain period (until, of course,
the entire zone expires).  If this makes some sense, we may be able to
develop a cleaner solution than serve-stale by expanding the
observation.

I'm not necessarily a fan of the specific approach described in
draft-tale-dnsop-serve-stale, but I have to admit it's a practical
workaround (if not a "solution") for a real-world problem happening
today.  I'd be happier if the wg agrees on working on a better
solution, but in that case we should also be pragmatic.  That includes
the recognition that any protocol extension that requires changes to
both recursive and authoritative servers will take quite long to
deploy.  Since the problem is real and current, the solution should
have an intermediate state that might look a mere hack.

--
JINMEI, Tatuya


From nobody Fri Sep  8 17:32:53 2017
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6E812422F for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 17:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 XBFfxxrkHN1k for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 17:32:50 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E66A1201F8 for <dnsop@ietf.org>; Fri,  8 Sep 2017 17:32:50 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 4E59734B990; Sat,  9 Sep 2017 00:32:48 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 3DB1A216C1E; Sat,  9 Sep 2017 00:32:48 +0000 (UTC)
Date: Sat, 9 Sep 2017 00:32:48 +0000
From: Evan Hunt <each@isc.org>
To: Paul Vixie <paul@redbarn.org>
Cc: Joe Abley <jabley@hopcount.ca>, dnsop@ietf.org
Message-ID: <20170909003248.GD44967@isc.org>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8183111.Lxug4lBFgO@localhost.localdomain>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SgAePBuK1k3ZQfIhc6gII43_Z7U>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 00:32:52 -0000

On Thu, Sep 07, 2017 at 10:28:30PM -0700, Paul Vixie wrote:
> if they really need this, they should provide a method by which i can specify 
> both a TTL and an Expiry, and i will consider publishing both values, and
> if i do, then they can use them the way i intend them. because as i said,
> autonomy.  it's my data, and my TTL.

I agree, and yet, a DDoS can make your data unavailable for refresh
through no fault of yours, which makes a resolver operator appear to be
broken through no fault of theirs, which makes them want very much to
be able to do this bad thing.

So, TTL stretching goes on the pile with NXDOMAIN redirection, tools that
can be used for censorship, and all the other regrettable things that we
implemented anyway dammit.

(I do like the idea of advertising a separate expiry value though.)

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.


From nobody Fri Sep  8 18:43:58 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483431320CF for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 18:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Fki2aGsCuIzl for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 18:43:56 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4849212EC30 for <dnsop@ietf.org>; Fri,  8 Sep 2017 18:43:56 -0700 (PDT)
Received: from [10.199.2.125] (unknown [50.235.236.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 986DD61FA2; Sat,  9 Sep 2017 01:43:54 +0000 (UTC)
Message-ID: <59B34758.8020105@redbarn.org>
Date: Fri, 08 Sep 2017 18:43:52 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.18 (Windows/20170825)
MIME-Version: 1.0
To: Evan Hunt <each@isc.org>
CC: dnsop@ietf.org, Joe Abley <jabley@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org>
In-Reply-To: <20170909003248.GD44967@isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zTupF9H334ig4epSSbBc2mzTuMo>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 01:43:57 -0000

Evan Hunt wrote:
> On Thu, Sep 07, 2017 at 10:28:30PM -0700, Paul Vixie wrote:
>> if they really need this, they should provide a method by which i can specify
>> both a TTL and an Expiry, and i will consider publishing both values, and
>> if i do, then they can use them the way i intend them. because as i said,
>> autonomy.  it's my data, and my TTL.
>
> I agree, and yet, a DDoS can make your data unavailable for refresh
> through no fault of yours, which makes a resolver operator appear to be
> broken through no fault of theirs, which makes them want very much to
> be able to do this bad thing.

understood. this is the same reasoning that led comcast to argue for the 
ability to turn off dnssec for important zones (like jpl.nasa.gov) who 
had fubar'd their keys and/or signatures and/or delegated signers.

> So, TTL stretching goes on the pile with NXDOMAIN redirection, tools that
> can be used for censorship, and all the other regrettable things that we
> implemented anyway dammit.

not so fast. nxdomain redirection is an attack. censorship is an attack. 
i don't think you mean to group ttl stretching in with those attacks. 
because if you do, then we agree, it is an attack, and ought not be 
done, and certainly ought not be standardized in any form.

> (I do like the idea of advertising a separate expiry value though.)

i think if we're going to put something into the 20-year deployment 
funnel we should treat the fixed costs as high and demand more benefits. 
that's where the proposal up-thread came from.

-- 
P Vixie


From nobody Fri Sep  8 19:05:13 2017
Return-Path: <abbypan@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB801241FC for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 t3T12OuQSdw6 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:05:10 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05EFC132195 for <dnsop@ietf.org>; Fri,  8 Sep 2017 19:05:10 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id f199so12802548wme.0 for <dnsop@ietf.org>; Fri, 08 Sep 2017 19:05:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IyAOaIh3RZnt082PAj/OOShr1Ca1x6sWasB+iKMz0mA=; b=fuL0y/m3rsz19LUKVYyx3VBCij6hKcViPA0Wsr4uY9vCpn1m8sHlr16ujCSwfvWMUM uuG5O6yu45VBY+ZagFpmeoskGPvuzdNu8a2qL1gFi4jKCqtjmRw5/lBlq2N5xI7TFYaK RBBvUxvkLHShwOYVCd1F6f7VWNFNAahuJzPbllNgHvDMt+/R1o5f1Y+NkEgyiAOSBMfW woxq/7GbclWbNPAxS0972seZf5H6Vh+wFw3euzOr1CYt/a2Z7//BWXrkPZAcgtx+3yZ4 0ImrSoHna1gWVx9SMxLrXD5H1sXa5qvRY37ZJONFR55xMVOFQ7XyWejoiKT3xfqZrXaG XBxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IyAOaIh3RZnt082PAj/OOShr1Ca1x6sWasB+iKMz0mA=; b=hXhhvM/FXkUWcngV9faFFTMfAa4gLDhU/yWXM5OCGkd+BIqKhr0kdGM5XpADhZsr3i QlXKDrejWWzsNd3fEtLRoooUl3ZxaQ7TFQH/vrW1qnk4BKZmtK7sC6BWfQ7i015G3c39 rnBFERUIRXUblLybLC1vTrE5WDv4JG1PTWJDtLT/KZyc9Ha5nmPc+v+hStq5XWBbph37 5N7CqsiA/jwQLVM4XVINKfJYNEMnqzG5xOUAD7Ce6LkJX8RH+7+jKuN7hEfv/qc2ozEb VzkBj3l95Q4XRYD3qfZQOkRMtirksxLeWMxMRuiuR7PPlPvhivbYXFvpyJX1xZQ/x3sN JMpg==
X-Gm-Message-State: AHPjjUj9Jg2EMLRaZPVx+cknqFLH7E3qtnwMs4byyb9IScgI/j+Mu9xB AC2zNqqkt5JPOuF2vdWk4P+pjQ2BKQ==
X-Google-Smtp-Source: ADKCNb7iZp0STVLAAoW+GNeO5cpgyGUoI9OrqvqDvMYZ5OetDuCEd8lQeD+hYAQjU5PfsTC4WBWF4JHri1FxpgnXess=
X-Received: by 10.80.152.43 with SMTP id g40mr3615389edb.300.1504922708563; Fri, 08 Sep 2017 19:05:08 -0700 (PDT)
MIME-Version: 1.0
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <59b25fe5.a516c80a.c19c8.40e0SMTPIN_ADDED_BROKEN@mx.google.com>
In-Reply-To: <59b25fe5.a516c80a.c19c8.40e0SMTPIN_ADDED_BROKEN@mx.google.com>
From: Lanlan Pan <abbypan@gmail.com>
Date: Sat, 09 Sep 2017 02:04:57 +0000
Message-ID: <CANLjSvVePwqDgf6JBG=me85wLydcbS7+EOeuzQ5=2nEBpdy4RQ@mail.gmail.com>
To: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>,  Stephane Bortzmeyer <bortzmeyer@nic.fr>, tjw ietf <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045c1884755f270558b81fc2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FWntMPSfg0UYkoZ0yCs1c1CWIYU>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiBETlNPUCBDYWxsIGZvciBBZG9wdGlvbiAt?= =?utf-8?q?_draft-tale-dnsop-serve-stale?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 02:05:12 -0000

--f403045c1884755f270558b81fc2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) <ljsong@biigroup.cn>=E4=BA=8E2017=
=E5=B9=B49=E6=9C=888=E6=97=A5=E5=91=A8=E4=BA=94 =E4=B8=8B=E5=8D=885:16=E5=
=86=99=E9=81=93=EF=BC=9A

> I just notice it asks for "Standards Track" document. If it aims to
> introduce a special use of resolver to achieve some features for their
> users' benefit, I think informational document may be more appropriate ? =
I
> guess, like what RFC7706 does.
>

+1,  I support the adoption of this document if it is informational.

recursive can choose to support this "cache operation improvement feature"
or not, but not update 1034/1035's TTL definition.

recursive may use stale data/extend the TTL for some special scenario, for
example:

=3D=3Dnot ddos attack=3D=3D
1)  some domains' A TTL are set to 1s, and they will not change it, because
they think that will help new RR spreads faster...
recursives offen have to extend the TTL =3D 90s or 600s or 3600s.

2)  network temporary failure on resolution path ( recursive ->
authoritative ) , SERVFAIL / TIMEOUT, offen short time
trigger some "use stale bread" callback function to deal with the
SRRVFAIL/TIMEOUT failure,  the data is snapshot from online hot cache
LRU/cache aging heuristic.

=3D=3Dddos attack=3D=3D
3)  recursive encounter ddos attack
trigger "proxy top-N important domain's dns response" on the ddos
firewall,  the top-N important domain's data is generated from the whole
latest-M days query log.

4) important SLD authoritative encounter ddos attack
SLD authoritative wants recursives trigger above 2) solution on its hot
domains, for its most visited service.
SLD authoritative wants recursives have some knowledge about its subdomain
wildcards, to avoid not-visited subdomain wildcard failure.


> Davey
>
> > -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> > =E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:dnsop-bounces@ietf.org] =E4=
=BB=A3=E8=A1=A8 Stephane Bortzmeyer
> > =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B49=E6=9C=887=E6=97=A5=
 23:43
> > =E6=94=B6=E4=BB=B6=E4=BA=BA: tjw ietf
> > =E6=8A=84=E9=80=81: dnsop
> > =E4=B8=BB=E9=A2=98: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dn=
sop-serve-stale
> >
> > On Tue, Sep 05, 2017 at 03:25:39PM -0400,  tjw ietf <tjw.ietf@gmail.com=
>
> > wrote  a message of 77 lines which said:
> >
> > > This starts a formal Call for Adoption for
> > > draft-tale-dnsop-serve-stale
> > >
> > > The draft is available here:
> > > https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/
> >
> > I'm not enthousiastic. We should focus on making the DNS infrastructure
> more
> > reliable, not on adding something to a pile of already fragile protocol=
s.
> >
> > There is also an opportunity that it masks failures and prevents people
> from
> > properly assigning blame: "example.com works if I use Something Public
> DNS
> > but not if I use my ISP's resolver, therefore my ISP is broken".
> >
> > Also, the current draft does not make crystal-clear that stale data MUS=
T
> NOT
> > be served unless no authoritative name server replies.
> >
> > If it is adopted, I think that requesting some way to convey the fact i=
t
> is stale to
> > the client (Davey Song's message) is necessary.
> >
> > Regarding the draft, I'm surprised by the paragraph starting with "Paul
> Vixie
> > has suggested", paragraph which seems to completely ignore RFC 8020.
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
--=20
=E8=87=B4=E7=A4=BC  Best Regards

=E6=BD=98=E8=93=9D=E5=85=B0  Pan Lanlan

--f403045c1884755f270558b81fc2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">Davey =
Song(=E5=AE=8B=E6=9E=97=E5=81=A5) &lt;<a href=3D"mailto:ljsong@biigroup.cn"=
>ljsong@biigroup.cn</a>&gt;=E4=BA=8E2017=E5=B9=B49=E6=9C=888=E6=97=A5=E5=91=
=A8=E4=BA=94 =E4=B8=8B=E5=8D=885:16=E5=86=99=E9=81=93=EF=BC=9A<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">I just notice it asks for &quot;Standards Track=
&quot; document. If it aims to<br>
introduce a special use of resolver to achieve some features for their<br>
users&#39; benefit, I think informational document may be more appropriate =
? I<br>
guess, like what RFC7706 does.<br></blockquote><div><br></div><div>+1,=C2=
=A0 I support the adoption of this document if it is informational.<br></di=
v><div><br></div><div>recursive can choose to support this &quot;cache oper=
ation improvement feature&quot; or not, but not update 1034/1035&#39;s TTL =
definition.</div><div><br></div><div>recursive may use stale data/extend th=
e TTL for some special scenario, for example:</div><div><br></div><div>=3D=
=3Dnot ddos attack=3D=3D<br></div><div>1)=C2=A0 some domains&#39; A TTL are=
 set to 1s, and they will not change it, because they think that will help =
new RR spreads faster...</div><div>recursives offen have to extend the TTL =
=3D 90s or 600s or 3600s.</div><div><br></div><div>2)=C2=A0 network tempora=
ry failure on resolution path ( recursive -&gt; authoritative ) , SERVFAIL =
/ TIMEOUT, offen short time<br></div><div>trigger some &quot;use stale brea=
d&quot; callback function to deal with the SRRVFAIL/TIMEOUT failure,=C2=A0 =
the data is snapshot from  online hot  cache LRU/cache aging heuristic.</di=
v><div><br></div><div>=3D=3Dddos attack=3D=3D<br></div><div>3)=C2=A0 recurs=
ive encounter ddos attack</div><div> </div><div>trigger &quot;proxy top-N i=
mportant domain&#39;s dns response&quot; on the ddos firewall,=C2=A0 the to=
p-N important domain&#39;s data is generated from the whole  latest-M days =
query log.<br></div><div><br></div><div>4) important SLD authoritative enco=
unter ddos attack</div><div>SLD authoritative wants recursives trigger abov=
e 2) solution on its hot domains, for its most visited service.<br></div><d=
iv>SLD authoritative wants recursives have some knowledge about its subdoma=
in wildcards, to avoid not-visited subdomain wildcard failure.<br></div><di=
v> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Davey<br>
<br>
&gt; -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----<br>
&gt; =E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:<a href=3D"mailto:dnsop-bou=
nces@ietf.org" target=3D"_blank">dnsop-bounces@ietf.org</a>] =E4=BB=A3=E8=
=A1=A8 Stephane Bortzmeyer<br>
&gt; =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B49=E6=9C=887=E6=97=
=A5 23:43<br>
&gt; =E6=94=B6=E4=BB=B6=E4=BA=BA: tjw ietf<br>
&gt; =E6=8A=84=E9=80=81: dnsop<br>
&gt; =E4=B8=BB=E9=A2=98: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-d=
nsop-serve-stale<br>
&gt;<br>
&gt; On Tue, Sep 05, 2017 at 03:25:39PM -0400,=C2=A0 tjw ietf &lt;<a href=
=3D"mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>&gt;=
<br>
&gt; wrote=C2=A0 a message of 77 lines which said:<br>
&gt;<br>
&gt; &gt; This starts a formal Call for Adoption for<br>
&gt; &gt; draft-tale-dnsop-serve-stale<br>
&gt; &gt;<br>
&gt; &gt; The draft is available here:<br>
&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-tale-dnsop-serv=
e-stale/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/doc/draft-tale-dnsop-serve-stale/</a><br>
&gt;<br>
&gt; I&#39;m not enthousiastic. We should focus on making the DNS infrastru=
cture<br>
more<br>
&gt; reliable, not on adding something to a pile of already fragile protoco=
ls.<br>
&gt;<br>
&gt; There is also an opportunity that it masks failures and prevents peopl=
e<br>
from<br>
&gt; properly assigning blame: &quot;<a href=3D"http://example.com" rel=3D"=
noreferrer" target=3D"_blank">example.com</a> works if I use Something Publ=
ic DNS<br>
&gt; but not if I use my ISP&#39;s resolver, therefore my ISP is broken&quo=
t;.<br>
&gt;<br>
&gt; Also, the current draft does not make crystal-clear that stale data MU=
ST<br>
NOT<br>
&gt; be served unless no authoritative name server replies.<br>
&gt;<br>
&gt; If it is adopted, I think that requesting some way to convey the fact =
it<br>
is stale to<br>
&gt; the client (Davey Song&#39;s message) is necessary.<br>
&gt;<br>
&gt; Regarding the draft, I&#39;m surprised by the paragraph starting with =
&quot;Paul<br>
Vixie<br>
&gt; has suggested&quot;, paragraph which seems to completely ignore RFC 80=
20.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; DNSOP mailing list<br>
&gt; <a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
<br>
<br>
<br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=E8=87=B4=E7=
=A4=BC=C2=A0 Best Regards<br><br>=E6=BD=98=E8=93=9D=E5=85=B0=C2=A0 Pan Lanl=
an<br></div></div>

--f403045c1884755f270558b81fc2--


From nobody Fri Sep  8 19:17:16 2017
Return-Path: <phluid61@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58038132392 for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6ElcTPAnlUKV for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:17:13 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7075313235A for <dnsop@ietf.org>; Fri,  8 Sep 2017 19:17:13 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id j141so9010686ioj.4 for <dnsop@ietf.org>; Fri, 08 Sep 2017 19:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=t+LwKhuta8RQnK3xEo6/3eKBF7MyB3YzBA8YpNw91qg=; b=UoVVn4K82o2xbxB7CRym1P4wcFnlCuPKSs5OypYhHRt+o5CrdIP8xlFtpUG/pcWn9C I+19Rq89Tyjmtj92WDh+/I5Mqv4t+kk2CRo/ZUNz3g+bLopZl5H0+krW6iTfAxgXLMMH YxGUGo1Q4GrcwHnWxg8K++0XWK+Uq6DhroWNU3zLPFHF/OmMLeD1w/w7gma+FelAZevy dSChWfvEXFmP0ELHjfkIBY7I9J7ZgEez5L0dD+vJAvJQB9MWIVP8BvhiFL+dWjbW9oka K3MMpj/CAGz7bUINUko0OjWPFz17J4aaCG3DUL5BMEJT0TFb2N3L24O1QzbfhFF6CI5S 1Xmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=t+LwKhuta8RQnK3xEo6/3eKBF7MyB3YzBA8YpNw91qg=; b=azDbHQDJ6UsLuO4Nnt2zLhfpa7n/IqJ1R1HnIwiqI+HEPwpkkmR2+jrBsK2RUgiGUw BhY58g75LG6czZde0B12fj3x27bLcxj1WmCWc1AEzG9AOIGKGBhirTjicOzg8K4HxQgR A1iJXCUjkGnGHukv61KeJV+cSHbHDvJQTeSo/ZRZvoUmbcz11zlDB1Y+5jihrWBzb6dd HLUYsswSCMNXb+0+FLEttXEYpb5TwdRW/pmhON8JNYfIBo5Z4QLGgLPhpQB06LkMttpl DiMDgcb97Jqor3HAOs0ieAMrLwQwsBWWJ88dKhli9gGDK4dvjABx7DFZDmO3uvEmuI9Z kQsQ==
X-Gm-Message-State: AHPjjUiADrJ12ILlV9F9oVbn8TkcOS2TGxh0AuBZicYsZnbje3J5ry2A CDYGKigaQaIU5lp0Y5o7McKxrNNYOQ==
X-Google-Smtp-Source: AOwi7QCtzRKT4Yypjywl7NEXF1UjbFDenkaaA5KnvZ1qlMY/R/iHnVMoli+TncsNNqKWMKSt3Vj+Q7LWCRucCuZHv70=
X-Received: by 10.107.59.67 with SMTP id i64mr3241950ioa.123.1504923432627; Fri, 08 Sep 2017 19:17:12 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.38.70 with HTTP; Fri, 8 Sep 2017 19:17:11 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.11.1709081524290.2676@grey.csi.cam.ac.uk>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <alpine.DEB.2.11.1709081524290.2676@grey.csi.cam.ac.uk>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Sat, 9 Sep 2017 12:17:11 +1000
X-Google-Sender-Auth: Mi5-Y0tI0hRhpA-IBHnFcP0-8kQ
Message-ID: <CACweHNBPZaq5cDZqrT7J1q4i-JpPy5BcKEMH6QM-08DQDETw=Q@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Content-Type: multipart/alternative; boundary="94eb2c068b769db9310558b84ab6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7teupic0CP5sEsh6RfBzGVV3jxE>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 02:17:15 -0000

--94eb2c068b769db9310558b84ab6
Content-Type: text/plain; charset="UTF-8"

On 9 September 2017 at 00:32, Tony Finch <dot@dotat.at> wrote:

> Paul Vixie <paul@redbarn.org> wrote:
> >
> > if they really need this, they should provide a method by which i can
> specify
> > both a TTL and an Expiry, and i will consider publishing both values,
> and if i
> > do, then they can use them the way i intend them.
>
> RRSIG sort-of does that?
>
>
Perhaps there's value in looking at HTTP's Cache-Control frankenbeast,
particularly RFC 5861. Being able to specify stale-on-error /
stale-while-revalidate (or explicitly *not*) alongside a hard TTL could be
useful.

Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/

--94eb2c068b769db9310558b84ab6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif;color:rgb(7,55,99)"><br></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On 9 September 2017 at 00:32, Tony Finch <span dir=3D"lt=
r">&lt;<a href=3D"mailto:dot@dotat.at" target=3D"_blank">dot@dotat.at</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span=
 class=3D"gmail-">Paul Vixie &lt;<a href=3D"mailto:paul@redbarn.org">paul@r=
edbarn.org</a>&gt; wrote:<br>
&gt;<br>
&gt; if they really need this, they should provide a method by which i can =
specify<br>
&gt; both a TTL and an Expiry, and i will consider publishing both values, =
and if i<br>
&gt; do, then they can use them the way i intend them.<br>
<br>
</span>RRSIG sort-of does that?<br><div class=3D"gmail-HOEnZb"><div class=
=3D"gmail-h5"><br>
</div></div></blockquote></div><br><div class=3D"gmail_default" style=3D"fo=
nt-family:georgia,serif;color:rgb(7,55,99)">Perhaps there&#39;s value in lo=
oking at HTTP&#39;s Cache-Control frankenbeast, particularly RFC 5861. Bein=
g able to specify stale-on-error / stale-while-revalidate (or explicitly *n=
ot*) alongside a hard TTL could be useful.</div><div class=3D"gmail_default=
" style=3D"font-family:georgia,serif;color:rgb(7,55,99)"><br></div><div cla=
ss=3D"gmail_default" style=3D"font-family:georgia,serif;color:rgb(7,55,99)"=
>Cheers</div>-- <br><div class=3D"gmail_signature"><div dir=3D"ltr">=C2=A0 =
Matthew Kerwin<br>=C2=A0 <a href=3D"http://matthew.kerwin.net.au/" target=
=3D"_blank">http://matthew.kerwin.net.au/</a></div></div>
</div></div>

--94eb2c068b769db9310558b84ab6--


From nobody Fri Sep  8 19:49:23 2017
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA9113208E for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 iGUbAomlrb3A for <dnsop@ietfa.amsl.com>; Fri,  8 Sep 2017 19:49:21 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B32412ECEC for <dnsop@ietf.org>; Fri,  8 Sep 2017 19:49:21 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 1A8FC34B9D1; Sat,  9 Sep 2017 02:49:18 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 0E6B6216C1E; Sat,  9 Sep 2017 02:49:18 +0000 (UTC)
Date: Sat, 9 Sep 2017 02:49:18 +0000
From: Evan Hunt <each@isc.org>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org, Joe Abley <jabley@hopcount.ca>
Message-ID: <20170909024918.GA48842@isc.org>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org> <59B34758.8020105@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59B34758.8020105@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qigpkIlYXgIGWNujQc4JOUXhico>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 02:49:22 -0000

On Fri, Sep 08, 2017 at 06:43:52PM -0700, Paul Vixie wrote:
> not so fast. nxdomain redirection is an attack. censorship is an attack. 
> i don't think you mean to group ttl stretching in with those attacks. 
> because if you do, then we agree, it is an attack, and ought not be 
> done, and certainly ought not be standardized in any form.

They're both lies, and TTL stretching is a lie, and in principle I
believe the DNS should not lie, but filter-aaaa and dns64 and RPZ all
had good and worthy reasons, and nxdomain redirection had bad reasons
with dollar signs next to them, and here we are.

Just as with RPZ, it seems reasonable to publish guidance on how to
do the kind-of-bad thing in the least bad way.

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.


From nobody Sat Sep  9 08:29:34 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C581132932 for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 08:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 6Vx18tc_svHY for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 08:29:31 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9D62132339 for <dnsop@ietf.org>; Sat,  9 Sep 2017 08:29:31 -0700 (PDT)
Received: from [172.31.98.12] (23-24-118-27-static.hfc.comcastbusiness.net [23.24.118.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id BC87961FA2; Sat,  9 Sep 2017 15:29:30 +0000 (UTC)
Message-ID: <59B408D8.1050608@redbarn.org>
Date: Sat, 09 Sep 2017 08:29:28 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Evan Hunt <each@isc.org>
CC: dnsop@ietf.org, Joe Abley <jabley@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org> <59B34758.8020105@redbarn.org> <20170909024918.GA48842@isc.org>
In-Reply-To: <20170909024918.GA48842@isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SUzqTBdbN1XMxHBw0_hRdIWgKKU>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 15:29:33 -0000

Evan Hunt wrote:
> On Fri, Sep 08, 2017 at 06:43:52PM -0700, Paul Vixie wrote:
>> not so fast. nxdomain redirection is an attack. censorship is an attack.
>> i don't think you mean to group ttl stretching in with those attacks.
>> because if you do, then we agree, it is an attack, and ought not be
>> done, and certainly ought not be standardized in any form.
>
> They're both lies, and TTL stretching is a lie, and in principle I
> believe the DNS should not lie, but filter-aaaa and dns64 and RPZ all
> had good and worthy reasons, and nxdomain redirection had bad reasons
> with dollar signs next to them, and here we are.
>
> Just as with RPZ, it seems reasonable to publish guidance on how to
> do the kind-of-bad thing in the least bad way.

rpz is a defense. it assumes that the content owner is trying to hurt 
me. it is therefore one step away from being an attack, and is in any 
case, not an attack.

i think that attack-p is more relevant than lie-p for this discussion.

-- 
P Vixie


From nobody Sat Sep  9 11:06:14 2017
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC81132D42 for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 11:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 yz_meDIS_q6T for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 11:06:12 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4482D132D41 for <dnsop@ietf.org>; Sat,  9 Sep 2017 11:06:12 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id AEFC534BF96; Sat,  9 Sep 2017 18:06:08 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 9C22F216C1E; Sat,  9 Sep 2017 18:06:08 +0000 (UTC)
Date: Sat, 9 Sep 2017 18:06:08 +0000
From: Evan Hunt <each@isc.org>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org, Joe Abley <jabley@hopcount.ca>
Message-ID: <20170909180608.GA54580@isc.org>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org> <59B34758.8020105@redbarn.org> <20170909024918.GA48842@isc.org> <59B408D8.1050608@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59B408D8.1050608@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cPlM89J8ksyO2-0hvpa2j0kYdvM>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 18:06:13 -0000

On Sat, Sep 09, 2017 at 08:29:28AM -0700, Paul Vixie wrote:
> rpz is a defense. it assumes that the content owner is trying to hurt 
> me. it is therefore one step away from being an attack, and is in any 
> case, not an attack.

Sure.  And TTL stretching assumes the content owner is a fellow victim,
and someone is trying to hurt both of us by making their site inaccessible
to me.  Both are lies; both have a defensible moral justification.

> i think that attack-p is more relevant than lie-p for this discussion.

The line between attack and not-attack can be surprisingly blurry.  But
given that there are non-malevolent reasons for wanting to serve stale
data, and solutions are being implemented (including one in BIND), I'm
okay with publishing details of the method, same as with RPZ.

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.


From nobody Sat Sep  9 12:22:22 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67B3A132925 for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 12:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 nRjBejovfDMp for <dnsop@ietfa.amsl.com>; Sat,  9 Sep 2017 12:22:20 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C2F61321DE for <dnsop@ietf.org>; Sat,  9 Sep 2017 12:22:20 -0700 (PDT)
Received: from [10.199.2.125] (unknown [50.235.236.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 8A2E261FA2; Sat,  9 Sep 2017 19:22:19 +0000 (UTC)
Message-ID: <59B43F69.5060901@redbarn.org>
Date: Sat, 09 Sep 2017 12:22:17 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Evan Hunt <each@isc.org>
CC: dnsop@ietf.org, Joe Abley <jabley@hopcount.ca>
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org> <59B34758.8020105@redbarn.org> <20170909024918.GA48842@isc.org> <59B408D8.1050608@redbarn.org> <20170909180608.GA54580@isc.org>
In-Reply-To: <20170909180608.GA54580@isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yx37iJW9wh2goqeRsvUFxAFIvk8>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Sep 2017 19:22:21 -0000

Evan Hunt wrote:
> On Sat, Sep 09, 2017 at 08:29:28AM -0700, Paul Vixie wrote:
>> rpz is a defense. it assumes that the content owner is trying to hurt
>> me. it is therefore one step away from being an attack, and is in any
>> case, not an attack.
>
> Sure.  And TTL stretching assumes the content owner is a fellow victim,
> and someone is trying to hurt both of us by making their site inaccessible
> to me.  Both are lies; both have a defensible moral justification.

the content owner may have good and specific reasons for the TTL they 
chose, and using that data for longer than that period may be harmful, 
and must be presumed to be harmful unless explicit signaling is added to 
let the content owner specify otherwise.

autonomous, coherent, reliable, distributed: pick four.

-- 
P Vixie


From nobody Sun Sep 10 18:35:37 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4A35126DFE for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 18:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 pmDY1sNsgIYK for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 18:35:34 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FF15126BFD for <dnsop@ietf.org>; Sun, 10 Sep 2017 18:35:33 -0700 (PDT)
Received: (qmail 11690 invoked by uid 125); 11 Sep 2017 01:35:32 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 11 Sep 2017 01:35:32 -0000
Date: 11 Sep 2017 01:35:10 -0000
Message-ID: <20170911013510.17202.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20170907045934.C194B848328B@rock.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zLDI82FpmL5gG6KeXojVhI5iz7I>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 01:35:36 -0000

In article <20170907045934.C194B848328B@rock.dv.isc.org> you write:
>
>In message <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com>
>, Ted Lemon writes:
>> Mark, I really don't think this is a human rights issue. Is there something
>> that will break for you if the secure denial of existence is left in place?
>
>I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
>tools.  Lookups should "just work" like they did before the root
>zone was signed.

It seems to me that if someone has enough programming skill to write a
DNSSEC verifier for her cache or stub resolver, she has enough skill
to treat localhost as a special case.

Or she could use unbound which has done this for ages.

R's,
John


From nobody Sun Sep 10 21:29:25 2017
Return-Path: <songlinjian@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC22132CE8 for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 21:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1X45ksoeZAgJ for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 21:29:22 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF70A132D41 for <dnsop@ietf.org>; Sun, 10 Sep 2017 21:29:21 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id c27so9936111uah.2 for <dnsop@ietf.org>; Sun, 10 Sep 2017 21:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=hWYKPHRlZaL+Zy5/IGjaV+JS7ShcTKrugsMUywFBK9I=; b=GHLQSr5SH7sArmZ1VXMlvbCcxaBprQwHLxA8AHyt7Z47JzPfAj3ZOBOJGfAhKEWBLY iNFqCYFeu/0P2Mx6XDJXtPtaMcKCIG/S+ocX/fE4jt7pI/wAjLvzQ/Xi7/L5QGZ2GJLZ LBX0+v/x53uuqVZUZe3kvzwEsvGrbLDceUCII+cUvypxr//JdG6FfaJ+sUu8VFrH8bgV wwsUlvAqmnhjFKoKq1YYuDmSd6bZ6T+Sz2sf7OBEy0qybvNDMR/NVsA9+pvdnNvJfdcp rbe3tLA1nxBkplwLN38JQXT9EYZ2OdC75jfiyLmzBNGEEf4RWbdaaiBg1uHEqJUBPHpO i9nw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=hWYKPHRlZaL+Zy5/IGjaV+JS7ShcTKrugsMUywFBK9I=; b=P33kAyg7mAes8jIdcYLtXIzcowpqTp23UjO7iTcstc4VCRNZGaov7+toF3xp+maBFY LDeOG7gjpqjpT+baPWI16h3I/2SJlmPCZe1rZeEbX3RidsWfhvjL0VZ++egAc3+ixOmM TAVY+NQZne2p+XV/RlmkYMEI2sAA2SXnTi4lC9Hx//cRU24C4FVE3ZznWGy6kFP2Ucy2 2iDmJfysgJGhA5gy4eOrcSnYgUHW2tf5ooZoC4Cs9D05kgXmnaMyQZbQXo896iMVVMWv QlTJtTN6h3Jnmj8jN3CqopdyMrvrFC/vcjiCaBcOXBUZTaoblLLvmYBgRbIdClja/cst L32A==
X-Gm-Message-State: AHPjjUhmpUo+QaB1fXTbkIveOznGW9N+XtQrE0Aj7vis0y9l337KNaJX 7g63+w8u+w71ChdoLNzsfGgYHazZbQ==
X-Google-Smtp-Source: ADKCNb6Rk4HnuEzyxoeJZX7JLvG7eBDqZR+acmVX3MW7Rj43t4wmeRkyLIiz8g7te8GYGLjatSx06P6OQpd0byL5S+Y=
X-Received: by 10.176.7.148 with SMTP id c20mr8041047uaf.17.1505104160609; Sun, 10 Sep 2017 21:29:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.27.44 with HTTP; Sun, 10 Sep 2017 21:29:20 -0700 (PDT)
In-Reply-To: <150509601027.9852.16967877638602485585@ietfa.amsl.com>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com>
From: Davey Song <songlinjian@gmail.com>
Date: Mon, 11 Sep 2017 12:29:20 +0800
Message-ID: <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f8988d7dc1f0558e25e18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JXd617c48KB1umMHbAM_3R8YTxw>
Subject: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 04:29:24 -0000

--f403045f8988d7dc1f0558e25e18
Content-Type: text/plain; charset="UTF-8"

Hi folks,

I just submit a draft dealing with issue of large DNS response especially
in IPv6. Commnets are welcome.

If chairs think it is in the scope of dnsop wg and encourage us to discuss
it in this mailing list, I can submit it as a draft listed in dnsop wg.

Davey


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 11 September 2017 at 10:13
Subject: I-D Action: draft-song-atr-large-resp-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : ATR: Additional Truncated Response for Large DNS
Response
        Author          : Linjian Song
        Filename        : draft-song-atr-large-resp-00.txt
        Pages           : 8
        Date            : 2017-09-10

Abstract:
   As the increasing use of DNSSEC and IPv6, there are more public
   evidence and concerns on IPv6 fragmentation issues due to larger DNS
   payloads over IPv6.  This memo introduces an simple improvement on
   authoritative server by replying additional truncated response just
   after the normal large response.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [ATR-Github].  Comments and pull
   request are welcome.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-song-atr-large-resp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-song-atr-large-resp-00
https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--f403045f8988d7dc1f0558e25e18
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi folks,=C2=A0</div><div><br></div><div>I just submi=
t a draft dealing with issue of large DNS response especially in IPv6. Comm=
nets are welcome.=C2=A0</div><div><br></div><div>If chairs think it is in t=
he scope of dnsop wg and encourage us to discuss it in this mailing list, I=
 can submit it as a draft listed in dnsop wg.</div><div><br></div><div>Dave=
y</div><div>=C2=A0=C2=A0</div><br><div class=3D"gmail_quote">---------- For=
warded message ----------<br>From: <b class=3D"gmail_sendername"></b> <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-draft=
s@ietf.org</a>&gt;</span><br>Date: 11 September 2017 at 10:13<br>Subject: I=
-D Action: draft-song-atr-large-resp-00.txt<br>To: <a href=3D"mailto:i-d-an=
nounce@ietf.org">i-d-announce@ietf.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 ATR: Additional Truncated Response for Large DNS Response<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Linj=
ian Song<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-son=
g-atr-large-resp-00.<wbr>txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 8<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-09-10<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0As the increasing use of DNSSEC and IPv6, there are more publi=
c<br>
=C2=A0 =C2=A0evidence and concerns on IPv6 fragmentation issues due to larg=
er DNS<br>
=C2=A0 =C2=A0payloads over IPv6.=C2=A0 This memo introduces an simple impro=
vement on<br>
=C2=A0 =C2=A0authoritative server by replying additional truncated response=
 just<br>
=C2=A0 =C2=A0after the normal large response.<br>
<br>
=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the document with tes=
t<br>
=C2=A0 =C2=A0script is currently placed at GitHub [ATR-Github].=C2=A0 Comme=
nts and pull<br>
=C2=A0 =C2=A0request are welcome.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-song-atr-large-resp/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/dra=
ft-song-atr-large-resp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-song-atr-large-resp-00" rel=3D=
"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-song-=
atr-large-resp-00</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-=
00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>=
doc/html/draft-song-atr-large-<wbr>resp-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</a><br>
<br>
______________________________<wbr>_________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/m=
ailman/<wbr>listinfo/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shadow.<wbr>html<=
/a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel=3D"noreferrer"=
 target=3D"_blank">ftp://ftp.ietf.org/ietf/<wbr>1shadow-sites.txt</a><br>
</div><br></div>

--f403045f8988d7dc1f0558e25e18--


From nobody Sun Sep 10 23:11:44 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF1813217D for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 23:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 9YjWxu0o4jhK for <dnsop@ietfa.amsl.com>; Sun, 10 Sep 2017 23:11:42 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17CFB126BF3 for <dnsop@ietf.org>; Sun, 10 Sep 2017 23:11:42 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:e0e2:dee8:8f5f:3537] (unknown [IPv6:2001:559:8000:c9:e0e2:dee8:8f5f:3537]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id DA0FB61FA2; Mon, 11 Sep 2017 06:11:41 +0000 (UTC)
Message-ID: <59B6291C.20400@redbarn.org>
Date: Sun, 10 Sep 2017 23:11:40 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Davey Song <songlinjian@gmail.com>
CC: dnsop <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
In-Reply-To: <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dmeRq_ZHDRfxT83QeCilEIBQm_8>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 06:11:43 -0000

Davey Song wrote:
> Hi folks,
>
> I just submit a draft dealing with issue of large DNS response
> especially in IPv6. [Comments] are welcome.

in the original EDNS I-D, the following text was present:

> .IP MD
> ``More data'' flag.  Valid only in TCP streams where message ordering and
> reliability are guaranteed.  This flag indicates that the current message is
> not the complete request or response, and should be aggregated with the
> following message(s) before being considered complete.  Such messages are
> called ``segmented.''  It is an error for the RCODE (including the
> EXTENDED-RCODE), AA flag, or DNS Message ID to differ among segments of a
> segmented message.  It is an error for TC to be set on any message of a
> segmented message.  Any given RR must fit completely within a message, and
> all messages will both begin and end on RR boundaries.  Each section in a
> multipart message must appear in normal message order, and each section
> must be complete before later sections are added.  All segments of a message
> must be transmitted contiguously, without interleaving of other messages.

the MD extended flag was removed due to its complexity in 1998 or so, 
and while i planned to re-introduce it in EDNS2, however, EDNS1 never 
made it out the door, so it was lost.

i did not make it possible to use it in UDP because of packet reordering 
and because of microburst problems -- which is to say, TCP delivers 
things in the order they were transmitted, and attempts to avoid 
overloading the path bandwidth-delay-product (BDP) in ways that cause 
congestive loss.

by implication, MD was intended to allow messages larger than 64K 
octets, even while requiring individual RRsets to remain atomic within 
64K octet message segments. i realize that this is not the same goal 
you're pursuing with your draft, but this history may help you.

> If chairs think it is in the scope of dnsop wg and encourage us to
> discuss it in this mailing list, I can submit it as a draft listed in
> dnsop wg.

my own view is that changing the DNS protocol to work around middle 
boxes is a losing game. if measurement shows that a large fraction of 
today's deployed IPv6 edge does not accept extension headers or ICMP, 
and if that means fragmentation will not work toward those edges, then 
our proper response is to change all DNS servers to send extension 
headers on every IPv6 response. force the failures to occur as close as 
possible to, and as early as possible after, they are caused.

separately, we should be working on TFO deployment, and DNS-over-QUIC. 
we need a vision, rather than a long series of easy complications.

-- 
P Vixie


From nobody Mon Sep 11 04:59:46 2017
Return-Path: <matthijs@pletterpet.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0976013232C for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 04:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 18_cTO-3JtUF for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 04:59:43 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D74D132D22 for <dnsop@ietf.org>; Mon, 11 Sep 2017 04:59:43 -0700 (PDT)
Received: from [IPv6:2001:981:19be:1:58a:2293:1451:51da] (unknown [IPv6:2001:981:19be:1:58a:2293:1451:51da]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 1BDB7BA9C for <dnsop@ietf.org>; Mon, 11 Sep 2017 13:59:41 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none header.from=pletterpet.nl
To: dnsop@ietf.org
References: <ybl4luqq05v.fsf@w7.hardakers.net> <7d425067-84ff-2471-d39a-0c3a20c0116c@pletterpet.nl> <yblvakvn76v.fsf@w7.hardakers.net>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <b799e983-43d8-b6db-7a13-40c5cdf37800@pletterpet.nl>
Date: Mon, 11 Sep 2017 13:59:40 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <yblvakvn76v.fsf@w7.hardakers.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1NZ6_psbfxxL_ukYj2QPDqe1Xkc>
Subject: Re: [DNSOP] requesting WGLC for 5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 11:59:45 -0000

Wes,

On 06-09-17 18:05, Wes Hardaker wrote:
> Matthijs Mekking <matthijs@pletterpet.nl> writes:
> 
> Thanks for all your points, and I've gone through and handled them all
> in the text (including discussing that we update 7583 per your request).
> 
>> 2. waitTime only adds one queryInterval, while Itrp adds two. I believe
>> to be safe on the publishing side, two queryIntervals is needed. RFC
>> 7583 explains:
>>
>>    A validator will treat it as a trust anchor the next
>>    time it retrieves the RRset, a process that can take up to another
>>    queryInterval (the third term).
> 
> This is the one that had me think with a whiteboard for a while.  If I
> can sum it up differently, the problem is that 30 days may not be a
> factor of the queryInterval.  Thus:

But it is:

queryInterval = MAX(1 hr, MIN (15 days, 1/2*OrigTTL,
   1/2*RRSigExpirationInterval))

Since the 5011-enabled resolver should see at least two queries with the
new trust anchor, the 15 days (30/2) is in the above equation defined in
RFC 5011.


>     N * queryInterval >= >
> Where N is the number of queries to get somewhere over 30 days.

Sure, but N does not need to be higher than two, and in that case:

    2 * queryInterval = MAX(2 hr, MIN (30 days, OrigTTL,
RRSigExpirationInterval))

In other words, never more than 30 days.


> So Irtp is waiting an extra queryInterval to account for this
> possibility.

Right, and since it is a possibility, it should be taken into account.

An important observation is that once the add hold-down timer expires,
the new key will be added as a trust anchor *only* the next time the
validated RRset with the new key is seen at the resolver.

This is the reason why the second queryInterval must be part of the
equation.


> Mathematically, I think the actually time needed to wait is 30 %
> queryInterval, which may actually be 0 in some cases and just shy of
> queryInterval in others.  Sound about right?

I am sorry, I don't understand this logic, can you elaborate?

The way I see it, queryInterval is always at minimal 1 hr and at most 15
days (not taking into account retryTime).


Best regards,
  Matthijs



>> 4. Both definitions (Itrp and waitTime) don't really take into
>> consideration the retryTime defined in RFC 5011. Perhaps that can be
>> used for defining the extra safety margin.
> 
> I'll have to add some text about that.  I don't think we can solve the
> case for broken networks, though.  But it's an important point to bring up.
> 


From nobody Mon Sep 11 05:57:26 2017
Return-Path: <vladimir.cunat@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06299133047 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 05:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 1pMUt6i8X9T3 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 05:57:23 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C1DE132199 for <dnsop@ietf.org>; Mon, 11 Sep 2017 05:57:22 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:6cd9:b0ff:fe6b:acc8] (unknown [IPv6:2001:1488:fffe:6:6cd9:b0ff:fe6b:acc8]) by mail.nic.cz (Postfix) with ESMTPSA id A193C61753 for <dnsop@ietf.org>; Mon, 11 Sep 2017 14:57:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1505134639; bh=7Cebl8hmPLOrAi9C0i3sZujzoPkZe0f6HLIAJ3y+AMI=; h=To:From:Date; b=q0k/5QH28pMNwL5rCh7dVlx/Bt1ql47bRPZHEgdIsEaP/iljxuAmajClrpXPhNJGa yYlt3oYmZYevPzXhoUQQ5XBnIyVjPP813YGZRD/5wWa3CHYgI1toGKA7Dq9T0/Dxsp a2jKu7i+F8sbkxEcSam65rUpfBOPb+0rQGtHR3NM=
To: dnsop@ietf.org
References: <59B1F467.9010308@redbarn.org> <FAC87A99-5558-4369-ADC0-57E2B7BF0429@hopcount.ca> <8183111.Lxug4lBFgO@localhost.localdomain> <20170909003248.GD44967@isc.org> <59B34758.8020105@redbarn.org> <20170909024918.GA48842@isc.org> <59B408D8.1050608@redbarn.org> <20170909180608.GA54580@isc.org> <59B43F69.5060901@redbarn.org>
From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?= <vladimir.cunat+ietf@nic.cz>
Message-ID: <6843d8aa-0f6c-c312-4e06-4128a45d731b@nic.cz>
Date: Mon, 11 Sep 2017 14:57:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <59B43F69.5060901@redbarn.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/I6mL5PI8s-QsilWSduL4Q1_SEU0>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 12:57:25 -0000

On 09/09/2017 09:22 PM, Paul Vixie wrote:
> [...]
> the content owner may have good and specific reasons for the TTL they
> chose, and using that data for longer than that period may be harmful,
> and must be presumed to be harmful unless explicit signaling is added
> to let the content owner specify otherwise.

Requiring explicit signalling from authoritative servers, e.g. via EDNS,
might actually work in this case, as that side is also motivated to
implement and deploy support for stale-serving.  We would also avoid all
discussion around whether this needs to be on standards track and marked
as updating 1034+1035.

--Vladimir


From nobody Mon Sep 11 07:08:01 2017
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A621326ED for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 07:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 E_ENtrSO5mhh for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 07:07:55 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EE61132192 for <dnsop@ietf.org>; Mon, 11 Sep 2017 07:07:55 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id f199so40731695wme.0 for <dnsop@ietf.org>; Mon, 11 Sep 2017 07:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=eGuWjT9B3LfSznxhp/orsoCgMdhzNhfBS8aAAPaUmhY=; b=UNVd7n9bkygVM5h3dRXreaXRV3hAsYgKDaQsQsTizJnIDxlMjOmBwAUy1lM7pLHk14 Umlh5+hnlHjEFn1dTuN4rRTLbw6ad2KPSi9OQJDHsna72EBGjO9o08EiqBdcLldHuV7r bXdgHqQz2mR7J8WS8l7+MFCbOtgSDu8Fmb4xaiJDDxCULbpJakz3vTwJt+hSW9Ju8AZC 4mRfo7svbw1b3COfg4QFbFMFessH4xXBaqUM2aQGwPR0lcpL3DynkKdi7rZ2Ju49DbFS HnBMZdKq6J1MxJGYce/HYy3t943k+EtZU9Wq06YcqHIIXj1ngeYk2SeNhlrUWgCFCy9h yUnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=eGuWjT9B3LfSznxhp/orsoCgMdhzNhfBS8aAAPaUmhY=; b=bs7JFZLauGojXgt4P391hySfFONXHJHVA2UpLqQpDK0rJXzie//fBsO7CDisvrCZ0U uRiDKv/lZCYHpbY9vKuc7Qekip5RckRPURAMxf95+2SenOF6x7ZWZ0U6JEIWt5RxAMCZ GwHoBgYE/gocDUtVi/iQP5YliyVVpPcYxw8V7I1yDuLfV7zOG8HfWSycCyWeW1QKuix6 F07K0DLCW7tnWxs9T9dSRAv5x/pCq63AzYBalhgHXpBMXdX7mfSc+HG8Cv1t5+KzGtQA XMl2ngkYG613pJGZj6yFPGWikurZbxDJR643RbTR+Zv4t9B7IJE+BB624A5rcohkNTBz K54Q==
X-Gm-Message-State: AHPjjUjUiCCMXV0uEu70eMx0M2MR0/ThsCAp9c3faMkXM4PY71GgQS6N m3phEkKUwXgXePJzMr6YeDXfP6nXVSp0vJvoBhdz/g==
X-Google-Smtp-Source: AOwi7QAI7IzSnSnSwoKHuIAf6yUtcG6u7i82r3G/y6XQTPYlkmcwCp97s7UENIsNRIkVQMTjSdNDs/plhU4iw4GMHOY=
X-Received: by 10.28.211.66 with SMTP id k63mr1622234wmg.85.1505138873436; Mon, 11 Sep 2017 07:07:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.141 with HTTP; Mon, 11 Sep 2017 07:07:12 -0700 (PDT)
In-Reply-To: <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com> <24CD1C88-58C5-4D6C-9F00-E3A2CD8C657C@fugue.com> <CADyWQ+Ex23QVef3AegWB4Jgd-sjG-G4z7XmXL9guN8PeWtsssw@mail.gmail.com> <93C3A47F-07C4-443F-AB87-B5C29F6B6774@fugue.com> <CAHw9_iKBDY9hNThOY3GDeG7BbCkc8Ncy1T=rjpcQ=h5qdB7=UQ@mail.gmail.com> <20170907041659.ED0BB8482BFF@rock.dv.isc.org> <CAPt1N1kXeF0zj_VHuv00taZ+39hR6Nw19uZ5rdxJr3aUeS5RvQ@mail.gmail.com> <20170907045934.C194B848328B@rock.dv.isc.org> <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com> <20170908000559.DDBD7849CFAC@rock.dv.isc.org> <CAPt1N1kKNRU+mF-JVti_CKS25+7g5BFH8Yko53-VKgZqVreZuQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 11 Sep 2017 10:07:12 -0400
Message-ID: <CAHw9_iJL-Lc84GnMtOERM2oupVrMxKjoYGeumE9K77RwOE4uqQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Mark Andrews <marka@isc.org>, dnsop WG <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/507aWMPcqgSYnAl-Y0MNQYGNVIg>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 14:08:00 -0000

On Thu, Sep 7, 2017 at 10:17 PM, Ted Lemon <mellon@fugue.com> wrote:
> The discussion had covered the failure mode problem. There is substantial
> agreement that it's better for a stub that issues a query for localhost t=
o
> fail than to succeed. You seem to disagree.
>

I wonder if this is simply people talking past each other, and a lack
of agreement on what the behavior we actually want is.
When I first read the document, and at the beginning of this thread I
firmly believed that we would want an insecure delegation from the
root, but after more discussion on what we want the behavior of
'localhost' to be I've been convinced otherwise.

I think that this boils down to: It is an error to send a query for
localhost (or anything under localhost) to the DNS. The main reason
for this (at least from my reading of the thread) is a security
argument -- you want to be completely sure that 'localhost' will
always be 127.0.0.1 / ::1 / some local equivalent, and this is not a
guarantee we can expect from the DNS[0]. Because of this it is better
the have queries that accidentally *do* leak into the DNS get a
failure (NXDOMAIN) - this avoids having (security important) cases
work fine until there is an attacker.

Is this a reasonable summary? Perhaps once we agree if *is* the
behavior we want we'll have an easier time deciding exactly how...

W
[0]: Without at least DNSSEC, everyone validating, and a trusted
entity running a localhost zone.

> You haven't stated a reason for disagreeing=E2=80=94instead you've vigoro=
usly
> asserted that this is true. It's fine for you to do this, but if you were=
 to
> get your way, that would be exactly the bad outcome I want to avoid.
>
> So if there really is a problem here, it would be good for you to make it
> clear. Your stated desire to preserve flexibility makes sense to me, but =
it
> doesn't contradict the reason already given for not providing that
> flexibility.
>
> Is there some other reason why this is important to you, or is that it?
>
> On Sep 7, 2017 8:06 PM, "Mark Andrews" <marka@isc.org> wrote:
>>
>>
>> In message <BFAECDAF-8F4B-4C8D-AB7E-1615BD54EF93@fugue.com>, Ted Lemon
>> writes:
>> >
>> > On Sep 7, 2017, at 12:59 AM, Mark Andrews <marka@isc.org> wrote:
>> > > I shouldn't BE FORCED to hard code special LOCALHOST rules into DNS
>> > > tools.  Lookups should "just work" like they did before the root
>> > > zone was signed.
>> >
>> > Because...?
>>
>> Because there are things you can do with localhost as a DNS zone
>> that you can't do with /etc/hosts, NIS, etc. as they are limited
>> to addresses only.
>>
>> Localhost should work just like home.arpa.  The tools we use shouldn't
>> need special knowledge.  Special knowledge means EVERYTHING needs
>> to be tested to see if it works with localhost as well and regular
>> names.  That testing will get missed.  If it doesn't get missed it
>> costs more money.  Workarounds for different behavior increases the
>> probability of bugs being introduced as there will be seperate code
>> paths.
>>
>> If I want to add a local trust anchor for localhost I will then
>> need additional code to disable the workaround for the fact the
>> root doesn't have a insecure delegation.
>>
>> Mark
>> --
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org



--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Mon Sep 11 09:49:34 2017
Return-Path: <msj@nthpermutation.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC96132644 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 09:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.com
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 8JsQbM6s6ZRA for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 09:49:30 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A610132EBA for <dnsop@ietf.org>; Mon, 11 Sep 2017 09:49:30 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id r141so19800599qke.2 for <dnsop@ietf.org>; Mon, 11 Sep 2017 09:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=l9cbTcVbXvFpKDU4eTmPbetbYfpisUwide3yYHJz++U=; b=PT5KSr4dLs/w6J6hqB+OxyEaunhFiZ5ld2RitF5TInx2iF3EUUyvifnPm5vg1GZsMX niDjblJgpPPZvnlf1TP7nKWYXiDanRElIBqEkuJTW8zVhe4A9I9sPORp4crL65oLb80s sA8VoXFch81ogMtP04xltOd/vVbq6QvbnuM8tVpIBHqAk857+PfADRi+mLGdlxtglttH 1UQu90qPR+NuMiszoBEiBFxt1rXdzRNudo2dqQw8RXDUVZLKsVWFL4Dj9RN94hNXXPSO yagIS+l5Rkp+kSkeGdvAJavMxtj5TIbqbxE1T1+RXMuSFQ+It7SDEil1vvnMj/R4RFrN iDMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=l9cbTcVbXvFpKDU4eTmPbetbYfpisUwide3yYHJz++U=; b=IHNsemYpe62FD2XMvoN0v1teMVHI1pGj9ZQuEcMz0woNDZCKP0JTmhRZoR2zlOdN60 iewGz7PBvCY1jM2I4Ux1MCk/HiXeTQyhUgO+p04UkzjxtN9LgxooVUQ/R6Q2w2Pe/w6n 9ltj3dG1+el5KsZxePzxW1KmXogu6TpOkHu3NcklAAOQJrC68D3E8dSqhM0LOaDBrozH OPmRue0W2wY2dxOXvgx06WZojPBO1gsXQ4AAVZEfKDQfvrVDcrPbA6CMHFSzExIK6UhF dKmeSBfUbefpzdiAeWDXMh4AzvmwY/JHJaQQ/W8Q9j485AT9rvhRJt0vdPgSV6Es02BZ qiJw==
X-Gm-Message-State: AHPjjUhuZXIb8jZ99UIiPEgrdiTLE0O/WNeHNSB6mIkC8dqYu+R0DFlg WTpvfDp1nS19hRfJptI=
X-Google-Smtp-Source: AOwi7QBTa6yDd0Ifxo7oVdy4+Jn8IdM0NQ2e7pLrndeoPqFsgMOCnOCsIa22O9mcYLF1xb/+FwWDDg==
X-Received: by 10.55.174.65 with SMTP id x62mr16663936qke.200.1505148568988; Mon, 11 Sep 2017 09:49:28 -0700 (PDT)
Received: from [192.168.1.117] (c-69-140-114-191.hsd1.md.comcast.net. [69.140.114.191]) by smtp.gmail.com with ESMTPSA id t56sm6719358qte.54.2017.09.11.09.49.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Sep 2017 09:49:27 -0700 (PDT)
From: Michael StJohns <msj@nthpermutation.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: dnsop@ietf.org
References: <ybl4luqq05v.fsf@w7.hardakers.net> <CANeU+ZBzP+0REnZf0=_t60oXD_oA1nbYMRGcoFQ221buJb8YBw@mail.gmail.com> <ybly3s2le1m.fsf@w7.hardakers.net> <CANeU+ZD7NF07hZdsQT74bZar41dW6i2k6zaNvVnbRg0WYP4tMQ@mail.gmail.com> <yblmv8il906.fsf@w7.hardakers.net> <8c53d2b7-afe7-fe83-27b0-11297d896ad7@nthpermutation.com> <ybl1sptlazr.fsf@w7.hardakers.net> <a1af5a54-8d50-698d-71e2-87f6dbeb9ca2@nthpermutation.com> <yblo9sxpfb8.fsf@wu.hardakers.net> <yblh8yhmucf.fsf@wu.hardakers.net> <77997330-f10c-22b3-4683-68e6d2a37cc0@nthpermutation.com> <eef0317a-9be7-2eda-95b9-5fe716f8b981@nthpermutation.com>
Message-ID: <8e4ed0fd-9732-ccee-9119-05be00c97d9f@nthpermutation.com>
Date: Mon, 11 Sep 2017 12:49:24 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <eef0317a-9be7-2eda-95b9-5fe716f8b981@nthpermutation.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/54uLuvgdkEoskUhVSlmWalwcngc>
Subject: Re: [DNSOP] requesting WGLC for 5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 16:49:33 -0000

Wes/Warren - you still owe a response on the following.



On 7/19/2017 4:42 AM, Michael StJohns wrote:
> On date time vs intervals - I finally realized why Wes and I are 
> somewhat disconnected on this.
>
> 5011 was written as the protocol for the resolver and is totally 
> interval driven.   (E.g. query and retry timers are set and fire based 
> on when the resolver performs an action).
>
> This document is being written for the zone publishers, and the 
> process of publication is task driven and has humans as protocol 
> element timers.  The actual publication of a DNSSEC RRSIG is divorced 
> from both the date/time of creation and the RRSig's actual inception 
> and expiration dates.  While there is a defined interval between 
> inception and expiration, expiration occurs at a fixed point in time 
> and that point in time is independent from the interval between 
> publication and receipt by the client.
>
> In other words - the correct (or at least better and less subject to 
> being misunderstood) way of describing the various points in time the 
> publisher should do something is by referencing the fixed point in 
> time (expiration) where both publisher and client agree that something 
> happens and then figuring other fixed points in time from that 
> point.   Or to restate it again - "A publisher must wait until June 
> 5th 2010" will always evaluate to the same date and time regardless of 
> who calculates it and when they calculate it; "A publisher must wait 
> 30 days" will not.
>
>
> So :
> "
> publicationAddWaitInterval :: = MAX (30 Days, originalTTL of NEW 
> DNSKEY RRSet) + MAX ( all calculated queryIntervals for OLD and new 
> RRSets)  + addSlopInterval
> queryInterval ::= MAX (1 hour, MIN (
>                                                 15 days,
>                                                .5 * expirationInterval 
> DNSKey RRSet,
>                                                .5 * originalTTL DNSKey 
> RRSet)
>                                           )
>
> expirationInterval :: = expirationDate - inceptionDate
> addSlopInterval ::= 2 * MAX(originalTTL of any  DNSKEY RRSet valid 
> during the transition process)
>
> The publicationAddWaitDateTime  is the date and time on which the 
> publisher can assume that most of the 5011 capable resolvers have 
> accomplished the addition of the new trust anchor to their trust 
> anchor sets.  That date is the addHoldDownTimeInterval AFTER the 
> latest in time signature expiration date of any RRSet without the new 
> key.  This includes both published and unpublished RRSets. Publishers 
> should refrain from creating or publishing DNSKEY RRSets signed 
> exclusively by a new key until after this date. Specifically, the 
> inception date of such an RRSig should be later than the 
> publicationAddWaitDateTime"
>
> The addHoldDownTimeInterval above differs from what is in 5.1 section 
> 2.4.1 in that this is the publishers view of when the new trust anchor 
> is accepted by the resolver which may differ from a specific resolvers 
> view (due to when things are actually sent and received).  Section 
> 2.4.1 has to be combined with the text in section 2.2 which states 
> that the key isn't added until after the next time it is seen after 
> the expiration of the add hold down. Also, the queryInterval term of 
> this calculation should be the maximum of any DNSKEY RRSet seen during 
> the transition - it's possible that the publisher may reduce the 
> intervals or increase the intervals between RRSets and this provides 
> the publisher with the worst case value that any given resolver should 
> be using.
>
>
> Let's not confuse resolver numbers with publisher numbers and spend a 
> bit of time to get the language clear correct and implementable.
>
> Mike
>
>
>
>
>


From nobody Mon Sep 11 11:11:32 2017
Return-Path: <rharolde@umich.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 339151331A3 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 BJLeiN12Nsad for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:11:27 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 768B3133191 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:11:27 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id s62so23317625ywg.0 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:11:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7TtKV6jSohYb3y1DYSzzViAaKvUWAOBMjFMgltNf1+E=; b=SXrgZUu2ZdnynglRcJmY1/tCDA4cHU6i44RT39jC0roBUwtTBQXbLElrxl2TwZMTrh LhV/dAh1gp5Ef77jj9RnZMswhcNKnSflwMsiLycsrlB7jiNacWHictBPVQK/1VL/UaCY c8tgoFJCQzWOqhyv9puCRzQB1Ttfk+gvsjsCiNh6LObprlcIkBFBhzleB4qGxT+PPybl CaYQfM2ukJQeNCVlzFUNGl1WoQwNYU84dt6cx8Z2+k5emp9l5WVa2f1Klo9/mlG2b+96 Hy1+LgJWeogmw6U9Ilt/n3RgnBJxvE3y/5Aq/Y8xlNqdLfieblc9w28J6p/5yLw47AXS A54A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7TtKV6jSohYb3y1DYSzzViAaKvUWAOBMjFMgltNf1+E=; b=U1DM3N5lfS+tUepU49YlQ3f/QeLAlXRGqgeI6Ms9AuLYeeimC7YRjgTf/2EAF0WSwu FLGyn8iW2x7bVndTtpZynE5fDCkFyu+xyO7VHflbgmpRqCn6M713Ow/YOepJEUF+r4DC TfzDDCwQnrxuNGx5SqVc3IIP4aM9t+P/3GyBMqxsnnR6wREYa+cQXYCh2mFBoY3wczk/ IlnQpkH0t6etP7fUZT+p/wKKmCJ0gNB1SXuo6o3tDMmIeoxDfDI+FI1SYsLC4cTDYiPA yz0kTi6yEfLMSHHTudUrIe79de4xRghRoCfJT0LwoI742HcMSHhvdgOlvqV14Ypv7PTq 0Mwg==
X-Gm-Message-State: AHPjjUhL1dnB7lYTJxMOUd8qp2nTtbr4E0LRfiQRVsoB7TibOYQ/5GCr wqLkMDzYe6m3bVI7n4WmPzWl7ZUgIP2B1gg=
X-Google-Smtp-Source: ADKCNb7EPRvd8QebxYYV/Wje2cR/LtgnpaIKEL8p1ixjltU1LJZSdIooDuAkUEmsq7HT8OdRMELxf2VAewpdIqq9pe0=
X-Received: by 10.129.90.3 with SMTP id o3mr10971076ywb.396.1505153486327; Mon, 11 Sep 2017 11:11:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.118.16 with HTTP; Mon, 11 Sep 2017 11:11:25 -0700 (PDT)
In-Reply-To: <20170908020710.0170284A3195@rock.dv.isc.org>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net> <8295055.TIQDDEhZcU@localhost.localdomain> <20170907221241.GA1031@puck.nether.net> <20170908020710.0170284A3195@rock.dv.isc.org>
From: Bob Harold <rharolde@umich.edu>
Date: Mon, 11 Sep 2017 14:11:25 -0400
Message-ID: <CA+nkc8CaJ+4_SCwm5Nbvd8r5SaKcTFhRq4jNV8RHp91Mrt5BhA@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11491bd4e2ab3b0558eddaac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/y2zkqwL-0Th1PZ2ETqahoC9Gg5E>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 18:11:30 -0000

--001a11491bd4e2ab3b0558eddaac
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 7, 2017 at 10:07 PM, Mark Andrews <marka@isc.org> wrote:

>
> Part of the problem is that we have one TTL value for both freshness
> and don't use beyond.
>
> This is fixable.  It is possible to specify two timer values.  It
> does require adding signaling between recursive servers and
> authoritative servers, on zone transfers and update requests.
>
> You basically add a additional timer field to every record immediately
> after the TTL field.  This is only returned if the client has
> signalled support for the extended field, I suggest using the last
> DNS header bit for this as you can determine how you will parse the
> response base on whether the bit is set in the response or not.
> This field is used to expire records from the cache and its value
> is set to the TTL field if the server has learnt the record from
> server that doesn't support the extension.
>
> The existing TTL field is used for freshness checking.  When a query
> comes in after that value has expired a freshness check is performed
> similar to the existing prefetches that happen today.  A TTL of 1
> is returned unless the original TTL was 0 in which case 0 is returned.
>
> New client - new recursive server - new authservers
>
>         example.com. 300 86400 IN A 1.2.3.4
>
>                 +300 seconds
>
>         example.com. 1 86100 IN A 1.2.3.4
>          (background query is in process)
>
> Old client - new recursive server - new authservers
>
>         example.com. 300 IN A 1.2.3.4
>
>                 +300 seconds
>
>         example.com. 1 IN A 1.2.3.4
>          (background query is in process)
>
> New client - new recusive server - old auth servers
>
>         example.com. 300 300 IN A 1.2.3.4
>
>                 +300 seconds
>          (record has expired from cache,
>           new query is performed)
>
>         example.com. 300 300 IN A 1.2.3.4
>
> For UPDATE a replacement opcode would be cleanest way to signal the
> new format is being used.  NOTIMP should be returned by servers
> that don't support the new opcode.
>
> There will be a few broken servers that just echo back the new
> header bit.
>
> This way the authoritative servers still control how long records
> are stored for.  Dead servers will get a little bit of traffic until
> the the refresh completes.  If the authorative servers are under
> attack the clients still see a answer.
>
> The alternative is to perform the refresh query and if it fails to
> complete within X milliseconds return the cached data rather than
> returning the cached data and doing the refresh in the background.
>
> Mark
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

While I like the idea of a  "don't use beyond" timer, I think it will be a
very long time before it is widely deployed (and actually configured by
zone owners), and therefore won't solve our immediate need.  It would be
great if clients could opt-in, but again I don't see that happening anytime
soon.  So I would start with resolver-operators deciding what seems best
for their clients (which is hat is happening whether we like it or not).
Adding client opt-out/opt-in would be good.   Signalling to say that a
response is stale would be good.  Adding the second timer (both per-RR and
as a zone default value, like TTL is handled) would be good.

On a related note - the SOA "expire" timer tells a slave how long to keep
serving "stale" zone data when the master cannot be reached.  Would that be
a reasonable default value for how long a resolver should serve "stale"
data when the authoritative servers cannot be reached?   (Currently I think
most people set a very high value compared to the TTL.)

-- 
Bob Harold

--001a11491bd4e2ab3b0558eddaac
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure"><br></div></div><div class=3D"gmail_quote">On Thu, Sep 7, 2017 at 10:0=
7 PM, Mark Andrews <span dir=3D"ltr">&lt;<a href=3D"mailto:marka@isc.org" t=
arget=3D"_blank">marka@isc.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><br>
Part of the problem is that we have one TTL value for both freshness<br>
and don&#39;t use beyond.<br>
<br>
This is fixable.=C2=A0 It is possible to specify two timer values.=C2=A0 It=
<br>
does require adding signaling between recursive servers and<br>
authoritative servers, on zone transfers and update requests.<br>
<br>
You basically add a additional timer field to every record immediately<br>
after the TTL field.=C2=A0 This is only returned if the client has<br>
signalled support for the extended field, I suggest using the last<br>
DNS header bit for this as you can determine how you will parse the<br>
response base on whether the bit is set in the response or not.<br>
This field is used to expire records from the cache and its value<br>
is set to the TTL field if the server has learnt the record from<br>
server that doesn&#39;t support the extension.<br>
<br>
The existing TTL field is used for freshness checking.=C2=A0 When a query<b=
r>
comes in after that value has expired a freshness check is performed<br>
similar to the existing prefetches that happen today.=C2=A0 A TTL of 1<br>
is returned unless the original TTL was 0 in which case 0 is returned.<br>
<br>
New client - new recursive server - new authservers<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 300 86400 IN A 1.2.3.4<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +300 seconds<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 1 86100 IN A 1.2.3.4<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(background query is in process)<br>
<br>
Old client - new recursive server - new authservers<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 300 IN A 1.2.3.4<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +300 seconds<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 1 IN A 1.2.3.4<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(background query is in process)<br>
<br>
New client - new recusive server - old auth servers<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 300 300 IN A 1.2.3.4<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +300 seconds<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(record has expired from cache,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 new query is performed)<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://example.com" rel=3D"noreferre=
r" target=3D"_blank">example.com</a>. 300 300 IN A 1.2.3.4<br>
<br>
For UPDATE a replacement opcode would be cleanest way to signal the<br>
new format is being used.=C2=A0 NOTIMP should be returned by servers<br>
that don&#39;t support the new opcode.<br>
<br>
There will be a few broken servers that just echo back the new<br>
header bit.<br>
<br>
This way the authoritative servers still control how long records<br>
are stored for.=C2=A0 Dead servers will get a little bit of traffic until<b=
r>
the the refresh completes.=C2=A0 If the authorative servers are under<br>
attack the clients still see a answer.<br>
<br>
The alternative is to perform the refresh query and if it fails to<br>
complete within X milliseconds return the cached data rather than<br>
returning the cached data and doing the refresh in the background.<br>
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
Mark<br>
<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</font></span><div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"></div></d=
iv></blockquote><div>=C2=A0</div><div>While I like the idea of a=C2=A0 &quo=
t;don&#39;t use beyond&quot; timer, I think it will be a very long time bef=
ore it is widely deployed (and actually configured by zone owners), and the=
refore won&#39;t solve our immediate need.=C2=A0 It would be great if clien=
ts could opt-in, but again I don&#39;t see that happening anytime soon.=C2=
=A0 So I would start with resolver-operators deciding what seems best for t=
heir clients (which is hat is happening whether we like it or not).=C2=A0 A=
dding client opt-out/opt-in would be good.=C2=A0 =C2=A0Signalling to say th=
at a response is stale would be good.=C2=A0 Adding the second timer (both p=
er-RR and as a zone default value, like TTL is handled) would be good.</div=
><div><br></div><div>On a related note - the SOA &quot;expire&quot; timer t=
ells a slave how long to keep serving &quot;stale&quot; zone data when the =
master cannot be reached.=C2=A0 Would that be a reasonable default value fo=
r how long a resolver should serve &quot;stale&quot; data when the authorit=
ative servers cannot be reached?=C2=A0 =C2=A0(Currently I think most people=
 set a very high value compared to the TTL.)</div><div><br></div><div>--=C2=
=A0</div><div>Bob Harold</div><div><br></div></div><br></div></div>

--001a11491bd4e2ab3b0558eddaac--


From nobody Mon Sep 11 11:22:33 2017
Return-Path: <msj@nthpermutation.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4571331CB for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.402
X-Spam-Level: **
X-Spam-Status: No, score=2.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_SUMOF=5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.com
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 GucNmkxnEw9O for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:22:28 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2C651331C1 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:22:27 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id b23so20416988qkg.1 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=kOz2X2VFyN1q+i3h7HSqRpGe0bHiQPuwsUgqT4KLZAo=; b=NkOsQzTyvLTM7urISNawxY1elSCwZE2tvUfPk6USoDnnu8gzwjVcK4HvaTGF8DkkhZ NzkLxrX1LKG5zhbdBk0AkAYA8QbxkJ7u7kkOmOM/E51XkBVEoA5RDIYM/gsu2tRB8y8e Up3kDboIanZuYa1xzdoKT/h2KqhBHUj/W1PDBp1nrIgA/ZY79lAM98Z5pE0I4Xt8FSqs jOTNtS6b7oSUvvAw9tR6ZluSz4DkhAyLGAOMT2SWzZymNhwp9fSZ6ENha5sG7a94rx+Z PwVBPXDKrOTiz+BAonxR8KD2l4em2rGdKoLyPiq3jQomoshrmrZsyD9nhLUoE3E94MsY xFJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=kOz2X2VFyN1q+i3h7HSqRpGe0bHiQPuwsUgqT4KLZAo=; b=ex5iX/gVyBQYFvCO7MbJzXkq4Psr7NvCrDalhEo4JaT27s9zCr/BYIUxsW9sbqQSO7 p31h6zJ66fUYRbNH8/f5HmMJaqxRLLlS2IEJqaBTkzoDRc9J2G4X/OWIz7Q6w9UPE0Wb 9bHSlJQRNiHG9mcrIr3Ojsi/CvD5FxMOZTPA2m82iZvXrCeekS4a9JBQl+ygbK9NLvEY G9CjsABPWUAXdZlpu0QQ0bEFSTJy02/2DCv8a6/zOCZTXOWOKgI7bVP2+CC/YtbELYV9 AA9PF4PcvOvkZ7i6KyJJPGq1NV57iZZFVeEFYLqnX4EQiN0/7aJtiYqUt+5L+NHs9Mzr lf7w==
X-Gm-Message-State: AHPjjUhbLx0rsOLzYd6wY8WQ8b+GX/FLxSUvXLQQJfTU10rcaaamNIkD f/mD4bBWGK3ER7g2S0k=
X-Google-Smtp-Source: AOwi7QD7yoSAP2xNXlm/Se1eg97qdR8cOWRVn2AK/mRdydhJ0zQ/k6/kb3CqyEZY3HHPHYUw+EPUWQ==
X-Received: by 10.55.140.132 with SMTP id o126mr15611605qkd.126.1505154146468;  Mon, 11 Sep 2017 11:22:26 -0700 (PDT)
Received: from [192.168.1.117] (c-69-140-114-191.hsd1.md.comcast.net. [69.140.114.191]) by smtp.gmail.com with ESMTPSA id j206sm6370277qke.7.2017.09.11.11.22.25 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Sep 2017 11:22:25 -0700 (PDT)
To: dnsop@ietf.org
References: <ybl4luqq05v.fsf@w7.hardakers.net> <7d425067-84ff-2471-d39a-0c3a20c0116c@pletterpet.nl> <yblvakvn76v.fsf@w7.hardakers.net>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <d1d66a66-2972-c9d8-c22f-bcf341e6097d@nthpermutation.com>
Date: Mon, 11 Sep 2017 14:22:23 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <yblvakvn76v.fsf@w7.hardakers.net>
Content-Type: multipart/alternative; boundary="------------1A2847A2F9CC7944810D6E47"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mJXe3byqH5-fvCe2mpKGVpUro5I>
Subject: Re: [DNSOP] requesting WGLC for 5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 18:22:30 -0000

This is a multi-part message in MIME format.
--------------1A2847A2F9CC7944810D6E47
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 9/6/2017 12:05 PM, Wes Hardaker wrote:
> Matthijs Mekking <matthijs@pletterpet.nl> writes:
>
> Thanks for all your points, and I've gone through and handled them all
> in the text (including discussing that we update 7583 per your request).
>
>> 2. waitTime only adds one queryInterval, while Itrp adds two. I believe
>> to be safe on the publishing side, two queryIntervals is needed. RFC
>> 7583 explains:
>>
>>     A validator will treat it as a trust anchor the next
>>     time it retrieves the RRset, a process that can take up to another
>>     queryInterval (the third term).
> This is the one that had me think with a whiteboard for a while.  If I
> can sum it up differently, the problem is that 30 days may not be a
> factor of the queryInterval.  Thus:
>
>      N * queryInterval >= 30
>
> Where N is the number of queries to get somewhere over 30 days.
>
> So Irtp is waiting an extra queryInterval to account for this
> possibility.
>
> Mathematically, I think the actually time needed to wait is 30 %
> queryInterval, which may actually be 0 in some cases and just shy of
> queryInterval in others.  Sound about right?

*bleah*  This is the problem with trying to do the publisher math from 
the resolver's point of view.

In the following lower case terms are intervals, uppercase terms are 
date/times.  The difference between two date/times is an interval. The 
sum of an interval and a date/time is a date/time.

A given resolver - absent an attack (and missing packets) - installs a 
new trust anchor at this point in time (assuming the new stuff was 
published after LastQueryTime)

    LastQueryTime + queryInterval + addHoldDownTime + queryInterval.


With an attack (but absent missing packets), the new trust anchor is 
installed   at this point in time:

    RRSigExpirationTime + (queryInterval - MIN(0, RRSetExpirationTime -
    LastQueryTimePriorToRRSetExpiration )) + addHoldDownTime + queryInterval


The publisher, to calculate how long it should wait before assumes that 
most resolvers have installed the new trust anchor has to be able to 
calculate both queryInterval and addHoldDownTime and then take a SWAG as 
to how much longer to wait.  So assuming worst case we

Substitute queryInterval for

    (queryInterval - MIN(0, RRSetExpirationTime -
    LastQueryTimePriorToRRSetExpiration))

(Assuming that the RRSetExpiration happens infinitesimally after to the 
expiration of the query timer). That gets you the latest time the 
resolver might install a new trust anchor (without retries):

    RRSigExpirationTime + queryInterval + addHoldDownTime + queryInterval.

queryInterval starts as the 5011 formulation: queryInterval = MAX(1 hr, 
MIN (15 days, 1/2*origTTL, 1/2*  rrSigExpirationInterval))  but we have 
to deal with a possible disconnect here.  The notation is made that 
maxOldRRSigExpirationInterval is the maximum rrSigExpiratonInterval of 
the DNSKeyRRSets published prior to the RRSigExpirationTime.    The 
reason for this is to deal with the case where the publisher changes the 
rrSigExpirationInterval for the new DNSKeyRRSets and where it might be 
unclear which of multiple possible queryIntervals the resolver is using.

So:

    publishersQueryIntervalEstimate ::= MAX (1hr, MIN (15 days, 1/2*
    origTTL, 1/ * maxOldRRsigExpirationInterval))


addHoldDownTime starts as the 5011 formulation: "The add hold-down time 
is 30 days or the expiration time of the original TTL of the first trust 
point DNSKEY RRSet that contained the new key, whichever is greater." 
and gets converted into an actual formula:

    publishersAddHoldDownEstimate ::= MAX (30 days, origTTL).


So putting it all together we get:

    OldRRSigExpirationTime ::= the latest expiration date of an RRSig
    over an DNSKey RRSet which did not contain the new anchor.


    PublishersAddCompleteEstimatedDate ::= OldRRSigExpirationTime + 2 *
    publishersQueryIntervalEstimate + publishersAddHoldDownEstimate


That gets us a date on which well behaving resolvers should have gotten 
the word. But we need safety so:

    PublishersAddCompleteSafeDate ::= PublishersAddCompleteEstimatedDate
    + publishersSlop.


For want of a better value we use publishersSlop ::= 2 * 
publishersQueryIntervalEstimate making the final formula:

    PublishersAddCompleteSafeDate ::= OldRRSigExpirationTime + (4 *
    publishersQueryIntervalEstimate) + publishersAddHoldDownEstimate


So assuming:

    Today ::= 11 September 2017, Noon UTC

    OldRRSigExpirationTime ::= 18 September 2017, Noon UTC

    maxOldRRSigExpirationInterval (from the draft 5.1): 10 days.

    origTTL ::= 1 day


We get:

         publishersQueryIntervalEstimate:  MAX (1 hr, MIN (15 days, 12
    hrs, 5 days)) or 12 hrs.
         publishersAddHoldDownEstimate: MAX (30 days, 1 day) or 30 days.
         PublishersAddCompleteEstimatedDate: 201709181200 + 1 day + 30
    days or 201710191200
         PublishersAddCompleteSafeDate: 201709181200 + 2 days + 30 days
    or 201710201200

The actual interval to wait is PublishersAddCompleteSafeDate - Today or 
201710201200 - 201709111200 or 38 days assuming that you publish as soon 
as you sign.  (which is generally a bad assumption and why I keep 
pushing to use dates not intervals as the results).

Using instead some larger values:

    Today ::= 11 September 2017 Noon UTC
    OldRRSigExpirationTime ::= 30 September 2017 Noon UTC
    maxOldRRSigExpirationInterval:  45 days
    origTTL ::= 7 days

We get:

    publishersQueryIntervalEstimate: MAX (1 hr, MIN (15 Days, 3.5 days,
    22.5 days)) or 3.5 days
    publishersAddHoldDownCompleteEstimatedDate: MAX (30 days, 7 days) or
    30 days
    PublishersAddCompleteEstimatedDate:  201709301200 + 7 days + 30 days
    we get 201711061200
    PublishersAddCompleteSafeDate: 201709301200 + 14 days + 30 days we
    get 201711131200

Note that the safe dates can be calculated without reference to the 
current date, and without a need to back calculate an interval.

Mike









>
>> 4. Both definitions (Itrp and waitTime) don't really take into
>> consideration the retryTime defined in RFC 5011. Perhaps that can be
>> used for defining the extra safety margin.
> I'll have to add some text about that.  I don't think we can solve the
> case for broken networks, though.  But it's an important point to bring up.
>
Assume the worst case - that a resolver never goes into the fast retry 
mode.  Then you can just ignore the retryTime in favor of queryTime as a 
slop term.


Mike



--------------1A2847A2F9CC7944810D6E47
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 9/6/2017 12:05 PM, Wes Hardaker
      wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:yblvakvn76v.fsf@w7.hardakers.net">
      <pre wrap="">Matthijs Mekking <a class="moz-txt-link-rfc2396E" href="mailto:matthijs@pletterpet.nl">&lt;matthijs@pletterpet.nl&gt;</a> writes:

Thanks for all your points, and I've gone through and handled them all
in the text (including discussing that we update 7583 per your request).

</pre>
      <blockquote type="cite">
        <pre wrap="">2. waitTime only adds one queryInterval, while Itrp adds two. I believe
to be safe on the publishing side, two queryIntervals is needed. RFC
7583 explains:

   A validator will treat it as a trust anchor the next
   time it retrieves the RRset, a process that can take up to another
   queryInterval (the third term).
</pre>
      </blockquote>
      <pre wrap="">
This is the one that had me think with a whiteboard for a while.  If I
can sum it up differently, the problem is that 30 days may not be a
factor of the queryInterval.  Thus:

    N * queryInterval &gt;= 30

Where N is the number of queries to get somewhere over 30 days.

So Irtp is waiting an extra queryInterval to account for this
possibility.

Mathematically, I think the actually time needed to wait is 30 %
queryInterval, which may actually be 0 in some cases and just shy of
queryInterval in others.  Sound about right?</pre>
    </blockquote>
    <br>
    *bleah*  This is the problem with trying to do the publisher math
    from the resolver's point of view.<br>
    <br>
    In the following lower case terms are intervals, uppercase terms are
    date/times.  The difference between two date/times is an interval. 
    The sum of an interval and a date/time is a date/time.<br>
    <br>
    A given resolver - absent an attack (and missing packets) - installs
    a new trust anchor at this point in time (assuming the new stuff was
    published after LastQueryTime) <br>
    <blockquote>LastQueryTime + queryInterval + addHoldDownTime +
      queryInterval.   <br>
    </blockquote>
    <br>
    With an attack (but absent missing packets), the new trust anchor is
    installed   at this point in time:  <br>
    <blockquote>RRSigExpirationTime + (queryInterval - MIN(0,
      RRSetExpirationTime - LastQueryTimePriorToRRSetExpiration )) +
      addHoldDownTime + queryInterval<br>
    </blockquote>
    <br>
    The publisher, to calculate how long it should wait before assumes
    that most resolvers have installed the new trust anchor has to be
    able to calculate both queryInterval and addHoldDownTime and then
    take a SWAG as to how much longer to wait.  So assuming worst case
    we<br>
    <br>
    Substitute queryInterval for <br>
    <blockquote>(queryInterval - MIN(0, RRSetExpirationTime -
      LastQueryTimePriorToRRSetExpiration)) <br>
    </blockquote>
    (Assuming that the RRSetExpiration happens infinitesimally after to
    the expiration of the query timer). That gets you the latest time
    the resolver might install a new trust anchor (without retries):<br>
    <blockquote>RRSigExpirationTime + queryInterval + addHoldDownTime +
      queryInterval.<br>
    </blockquote>
    queryInterval starts as the 5011 formulation: queryInterval = MAX(1
    hr, MIN (15 days, 1/2*origTTL, 1/2*  rrSigExpirationInterval))  but
    we have to deal with a possible disconnect here.  The notation is
    made that maxOldRRSigExpirationInterval is the maximum
    rrSigExpiratonInterval of the DNSKeyRRSets published prior to the
    RRSigExpirationTime.    The reason for this is to deal with the case
    where the publisher changes the rrSigExpirationInterval for the new
    DNSKeyRRSets and where it might be unclear which of multiple
    possible queryIntervals the resolver is using.<br>
    <br>
    So:   <br>
    <blockquote>publishersQueryIntervalEstimate ::= MAX (1hr, MIN (15
      days, 1/2* origTTL, 1/ * maxOldRRsigExpirationInterval))<br>
    </blockquote>
    <br>
    addHoldDownTime starts as the 5011 formulation: "The add hold-down
    time is 30 days or the expiration time of the original TTL of the
    first trust point DNSKEY RRSet that contained the new key, whichever
    is greater." and gets converted into an actual formula:   <br>
    <blockquote>publishersAddHoldDownEstimate ::= MAX (30 days,
      origTTL).<br>
    </blockquote>
    <br>
    So putting it all together we get:<br>
    <br>
    <blockquote>OldRRSigExpirationTime ::= the latest expiration date of
      an RRSig over an DNSKey RRSet which did not contain the new
      anchor.<br>
    </blockquote>
    <br>
    <blockquote>PublishersAddCompleteEstimatedDate ::=
      OldRRSigExpirationTime + 2 * publishersQueryIntervalEstimate +
      publishersAddHoldDownEstimate<br>
    </blockquote>
    <br>
    That gets us a date on which well behaving resolvers should have
    gotten the word. But we need safety so:<br>
    <br>
    <blockquote>PublishersAddCompleteSafeDate ::=
      PublishersAddCompleteEstimatedDate + publishersSlop.<br>
    </blockquote>
    <br>
    For want of a better value we use publishersSlop ::= 2 *
    publishersQueryIntervalEstimate making the final formula:<br>
    <br>
    <blockquote>PublishersAddCompleteSafeDate ::= OldRRSigExpirationTime
      + (4 * publishersQueryIntervalEstimate) +
      publishersAddHoldDownEstimate<br>
    </blockquote>
    <br>
    So assuming:<br>
    <br>
    <blockquote>Today ::= 11 September 2017, Noon UTC<br>
      <br>
      OldRRSigExpirationTime ::= 18 September 2017, Noon UTC<br>
      <br>
      maxOldRRSigExpirationInterval (from the draft 5.1): 10 days.<br>
      <br>
      origTTL ::= 1 day<br>
    </blockquote>
    <br>
    We get:<br>
    <blockquote>    publishersQueryIntervalEstimate:  MAX (1 hr, MIN (15
      days, 12 hrs, 5 days)) or 12 hrs.<br>
          publishersAddHoldDownEstimate: MAX (30 days, 1 day) or 30
      days.<br>
          PublishersAddCompleteEstimatedDate: 201709181200 + 1 day + 30
      days or 201710191200<br>
          PublishersAddCompleteSafeDate: 201709181200 + 2 days + 30 days
      or 201710201200<br>
    </blockquote>
    The actual interval to wait is PublishersAddCompleteSafeDate - Today
    or 201710201200 - 201709111200 or 38 days assuming that you publish
    as soon as you sign.  (which is generally a bad assumption and why I
    keep pushing to use dates not intervals as the results).<br>
    <br>
    Using instead some larger values:<br>
    <br>
    <blockquote>Today ::= 11 September 2017 Noon UTC<br>
      OldRRSigExpirationTime ::= 30 September 2017 Noon UTC<br>
      maxOldRRSigExpirationInterval:  45 days<br>
      origTTL ::= 7 days<br>
      <br>
    </blockquote>
    We get: <br>
    <br>
    <blockquote>publishersQueryIntervalEstimate: MAX (1 hr, MIN (15
      Days, 3.5 days, 22.5 days)) or 3.5 days<br>
      publishersAddHoldDownCompleteEstimatedDate: MAX (30 days, 7 days)
      or 30 days<br>
      PublishersAddCompleteEstimatedDate:  201709301200 + 7 days + 30
      days we get 201711061200<br>
      PublishersAddCompleteSafeDate: 201709301200 + 14 days + 30 days we
      get 201711131200<br>
      <br>
    </blockquote>
    Note that the safe dates can be calculated without reference to the
    current date, and without a need to back calculate an interval.<br>
    <br>
    Mike<br>
    <br>
    <blockquote><br>
    </blockquote>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <blockquote type="cite" cite="mid:yblvakvn76v.fsf@w7.hardakers.net">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">4. Both definitions (Itrp and waitTime) don't really take into
consideration the retryTime defined in RFC 5011. Perhaps that can be
used for defining the extra safety margin.
</pre>
      </blockquote>
      <pre wrap="">
I'll have to add some text about that.  I don't think we can solve the
case for broken networks, though.  But it's an important point to bring up.

</pre>
    </blockquote>
    <p>Assume the worst case - that a resolver never goes into the fast
      retry mode.  Then you can just ignore the retryTime in favor of
      queryTime as a slop term.<br>
    </p>
    <p><br>
    </p>
    <p>Mike</p>
    <p><br>
    </p>
  </body>
</html>

--------------1A2847A2F9CC7944810D6E47--


From nobody Mon Sep 11 11:37:50 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DEAC132F29 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9kWKRCFDPfBk for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:37:47 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73C58132ECF for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:37:47 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id k2so20954892qte.2 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=cXiP2zSDNX2S16mzi0axjBih9tLMvYwck1zZAitUew8=; b=h6/H2b0OEBY5hz6s4ABncq/nr0jqwY9V2Hb72UPHkWJ1if47M8pliLBR6lV7kMFFvh ak0ZUdzB9ecADthLEA6N7hN6bjd3T8fXMuxD0/mVrzcfmzSObtSOn+cx1zqa6sohuVWA JveAIRF5EtitiiwJf38f/tORaJzQrp0O2fDNqLgw1m8AAxsrJ0Mo+hnVotp4b8sXiVqw 7ufyudkbN+YvriiRwMDURq0+9lZo5lUqJLu6ITIreEa7zQDy3kuI6D9FD6+4tSommiCI 1lUJN+s1CDYp6cSziIAayOj+ul1uctRXUHXSREPfGac8Yj7Upt5VUDPsZ0jxM21BqSAR 1DCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=cXiP2zSDNX2S16mzi0axjBih9tLMvYwck1zZAitUew8=; b=Jts3B3eMDvbmW7vVD/iZSwBOKIubIZNPbNyZuqDjNrqBi1H9irWCyl41yXGCBoObAM q0Xa55qkr54BWJng8wwfDbHRyWVO47kD5g4HmR2bCii5tiL1hQEGtQ5tz8m7gsiItGca KPgsNOKZFdCp6nmPInvQ1l+7iAahmDEuw8WLJJNHqGJVcDQTQwsrlspWTU76I4zT36Xt btst9aPUvaV84mYuBP6u7JKevI847WDLPx7p0TJBto34vteP9gcHjGa/6gI970uVaXuu rdFhSKaLLRdmJ/BUvdVFQJ0vxrKzVtVI9pRzbKjKUC/8nbD72XGXogepI+JjYthQQS91 d+5g==
X-Gm-Message-State: AHPjjUjgiUORmlqm7/i56fXsotFEIs2Kcr9y8l+OAKBGyN0SWBXCtkYD fWU/ATMcpe6SUaKFf+kEJcBWo7OuAg==
X-Google-Smtp-Source: AOwi7QDxcQ5b45xOwE0+NR067hpJq+MQabr2wl2Sr18TmOAx09dQuCKdQCq8zdmA645sikGP9vaA1FQAJR++nZPHfUA=
X-Received: by 10.237.61.221 with SMTP id j29mr18846205qtf.282.1505155066426;  Mon, 11 Sep 2017 11:37:46 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.200.54.104 with HTTP; Mon, 11 Sep 2017 11:37:45 -0700 (PDT)
In-Reply-To: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Mon, 11 Sep 2017 11:37:45 -0700
X-Google-Sender-Auth: dqDy6LxUYiLE2fovJqAq_qAT5J8
Message-ID: <CAJE_bqd3wQcXNmST0jKNBLBfyXrA-4Ee-BsdtLEuz5+0PwbwZA@mail.gmail.com>
To: tjw ietf <tjw.ietf@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4hwCVoghs8LiSb66zygui7ly4sQ>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 18:37:49 -0000

At Wed, 6 Sep 2017 10:00:01 -0400,
tjw ietf <tjw.ietf@gmail.com> wrote:

> When the idea of having a Call for Adoption for this document came up, we
> thought long and hard about this one.  However, the comments from the
> working group focused this document to address the specific issue of the
> local hostname.
>
> This starts a formal Call for Adoption for
> draft-west-let-localhost-be-localhost
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/
>
> Please review this draft to see if you think it is suitable for adoption by
> DNSOP, and comments to the list, clearly stating your view.

I've read draft-west-let-localhost-be-localhost-06.txt.  I don't have
a strong opinion on whether to adopt it, but if it's adopted I'm
willing to review subsequent versions.

I have one high-level comment: I wonder whether the name can be
different from "localhost".  My impression on some of the controversy
on this proposal is related to compatibility with the existing
practice with this name (e.g., some people may want to have their
preferred AAAA or A RDATA at their own risk).  If it can be a
completely new TLD we at least don't have to worry about that type of
conflict.  Of course this will require more procedural overhead such
as new registration for the special-use registry and doesn't help
any existing practice that assumes 'localhost' always means a
loopback address.  But such a practice is not 100% safe today anyway
(and in my understanding that's why this draft was written) and even
if the proposed new semantics for 'localhost' is standardized its
deployment will take time (and I suspect non-compliant behavior will
stay quite long).  So it might be even safer to introduce a new name
and have applications that need this property gradually migrate to it.

It's just a thought, I'm not pushing the idea.  But in any case, it
may be worth explaining in the draft why the name must be 'localhost'.

I have a couple of other minor comments on the current version.  All
of them are somehow related to how authoritative servers are supposed
to behave in the context of this draft:

- Section 1

   In addition, recursive and authoritative DNS servers are required to
   return "NXDOMAIN" for such queries.  This increases the likelihood

  Should authoritative servers other than the root server really be
  required to return NXDOMAIN?  Except for the root server, if an
  authoritative server receives a query for a name that doesn't belong
  to any zone it serves, it's generally considered a (some sense of)
  bogus query, and my understanding of common response to this kind of
  query is either REFUSED or a referral to the closest ancestor zone
  known to the server.  I don't see a reason for changing the behavior
  of these servers specifically for 'localhost'.

- Section 3

   5.  Authoritative DNS servers MUST respond to queries for localhost
       names with NXDOMAIN.

  Same comment applies.

- Section 4.2.1

   This document requests that a DNSSEC insecure delegation (that is, a
   delegation with no DS records) be inserted into the root-zone,
   delegated to "blackhole-[12].iana.org".

  This would violate the above 'MUST'.  If we choose this option (and
  if we also generally keep this MUST) some more clarification (such
  as making an exception) will be needed.

--
JINMEI, Tatuya


From nobody Mon Sep 11 11:52:12 2017
Return-Path: <mvavrusa@cloudflare.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDBD1331A3 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
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 f2jN7kMcrOSK for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 11:52:08 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19C28132697 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:52:08 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id 80so20889509lfy.4 for <dnsop@ietf.org>; Mon, 11 Sep 2017 11:52:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qh/jLYDjKdOVBKwc1QcXvJb37rpfT+Be45NNHRTZ6zc=; b=vdLBn4AxXsOKdaiK2W4yqFxeV27lkGHb8hGSHxPdS+EZkWQxvgQOdGEgCrG4NhR5v4 rSdyWa8kuF0YvzoN5niCaiI8RqKSR9Z+kQIgUvv3mPJ0w7if0LGDYUADY22XZUzu5Xlo /bdKqZUOYSK2C5uPzDqc0fTHSNzYkWp8al+XM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qh/jLYDjKdOVBKwc1QcXvJb37rpfT+Be45NNHRTZ6zc=; b=XnyNi+l/5xs8TyBpPsNwgN8/b+3Csfh5sKHHMo6qWRa1kWLFJVgqM/GmgTMj8eMU3H arHo4tgLGo3xZopzB6TJXT0wS+DKr7qUrkJ6M5INeRFSurvdRqSH2RZQuOyCAAbyQJpc ozE49CW8xBpC0SiT1TkfCh4gWVfhOw4YGl0S7BB/NY0nNCOA1dmKn1wd8baJ9DqG6s1X 5brqiCCFRSaxk/md3qVqfKKtsw9h1P5edfKuPwMq0evoqyUhgqZTo12uhqwYS7vKvrRu 4L88iz+xarIa7u+o6PBV6SMKBGfpkz//tz8Kh1mXLfPT47xPeSU+TFclAY/ArkxxnJ6T aUDg==
X-Gm-Message-State: AHPjjUjUQBtlh5OBWkr3XpJRhzKmXr5Ew7oDJLTg9iykN0KwZEsv4Kht paaSubAFCAoGZQmI5TJgf7X1Ciiul+WsDnU=
X-Google-Smtp-Source: AOwi7QDF4ypwGoCsHP0iVjxTQDHLrLr1dcf11g9PdBUehgGc5GDKLFUueiOSlbWpp7fYQ9/XrnL6loFiMKvekkIzi8A=
X-Received: by 10.25.23.105 with SMTP id n102mr4436131lfi.252.1505155926207; Mon, 11 Sep 2017 11:52:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.233.20 with HTTP; Mon, 11 Sep 2017 11:52:05 -0700 (PDT)
In-Reply-To: <CA+nkc8CaJ+4_SCwm5Nbvd8r5SaKcTFhRq4jNV8RHp91Mrt5BhA@mail.gmail.com>
References: <CADyWQ+FHDHcmq-mr0BCHS5A8yvaOQmhTjve1_DmZN6vAc=BKyA@mail.gmail.com> <20170907154234.3z2zbju2sciiy7wr@nic.fr> <ybltw0emmvh.fsf@wu.hardakers.net> <8295055.TIQDDEhZcU@localhost.localdomain> <20170907221241.GA1031@puck.nether.net> <20170908020710.0170284A3195@rock.dv.isc.org> <CA+nkc8CaJ+4_SCwm5Nbvd8r5SaKcTFhRq4jNV8RHp91Mrt5BhA@mail.gmail.com>
From: =?UTF-8?Q?Marek_Vavru=C5=A1a?= <mvavrusa@cloudflare.com>
Date: Mon, 11 Sep 2017 11:52:05 -0700
Message-ID: <CAC=TB12Y8nAPZAFy3WiXskuAzb+3cwR-Kqp_WoG8VPu+6AfuBg@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: Mark Andrews <marka@isc.org>, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gRzPomdqcuYE6m_nlEy7EDeNPQI>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-tale-dnsop-serve-stale
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 18:52:10 -0000

I support the adoption of this document. Was there a discussion of any
actual downsides besides "I'd like to know if it's stale" and
monitoring?

On Mon, Sep 11, 2017 at 11:11 AM, Bob Harold <rharolde@umich.edu> wrote:
>
> On Thu, Sep 7, 2017 at 10:07 PM, Mark Andrews <marka@isc.org> wrote:
>>
>>
>> Part of the problem is that we have one TTL value for both freshness
>> and don't use beyond.
>>
>> This is fixable.  It is possible to specify two timer values.  It
>> does require adding signaling between recursive servers and
>> authoritative servers, on zone transfers and update requests.
>>
>> You basically add a additional timer field to every record immediately
>> after the TTL field.  This is only returned if the client has
>> signalled support for the extended field, I suggest using the last
>> DNS header bit for this as you can determine how you will parse the
>> response base on whether the bit is set in the response or not.
>> This field is used to expire records from the cache and its value
>> is set to the TTL field if the server has learnt the record from
>> server that doesn't support the extension.
>>
>> The existing TTL field is used for freshness checking.  When a query
>> comes in after that value has expired a freshness check is performed
>> similar to the existing prefetches that happen today.  A TTL of 1
>> is returned unless the original TTL was 0 in which case 0 is returned.
>>
>> New client - new recursive server - new authservers
>>
>>         example.com. 300 86400 IN A 1.2.3.4
>>
>>                 +300 seconds
>>
>>         example.com. 1 86100 IN A 1.2.3.4
>>          (background query is in process)
>>
>> Old client - new recursive server - new authservers
>>
>>         example.com. 300 IN A 1.2.3.4
>>
>>                 +300 seconds
>>
>>         example.com. 1 IN A 1.2.3.4
>>          (background query is in process)
>>
>> New client - new recusive server - old auth servers
>>
>>         example.com. 300 300 IN A 1.2.3.4
>>
>>                 +300 seconds
>>          (record has expired from cache,
>>           new query is performed)
>>
>>         example.com. 300 300 IN A 1.2.3.4
>>
>> For UPDATE a replacement opcode would be cleanest way to signal the
>> new format is being used.  NOTIMP should be returned by servers
>> that don't support the new opcode.
>>
>> There will be a few broken servers that just echo back the new
>> header bit.
>>
>> This way the authoritative servers still control how long records
>> are stored for.  Dead servers will get a little bit of traffic until
>> the the refresh completes.  If the authorative servers are under
>> attack the clients still see a answer.
>>
>> The alternative is to perform the refresh query and if it fails to
>> complete within X milliseconds return the cached data rather than
>> returning the cached data and doing the refresh in the background.
>>
>> Mark
>>
>> --
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
>
> While I like the idea of a  "don't use beyond" timer, I think it will be a
> very long time before it is widely deployed (and actually configured by zone
> owners), and therefore won't solve our immediate need.  It would be great if
> clients could opt-in, but again I don't see that happening anytime soon.  So
> I would start with resolver-operators deciding what seems best for their
> clients (which is hat is happening whether we like it or not).  Adding
> client opt-out/opt-in would be good.   Signalling to say that a response is
> stale would be good.  Adding the second timer (both per-RR and as a zone
> default value, like TTL is handled) would be good.
>
> On a related note - the SOA "expire" timer tells a slave how long to keep
> serving "stale" zone data when the master cannot be reached.  Would that be
> a reasonable default value for how long a resolver should serve "stale" data
> when the authoritative servers cannot be reached?   (Currently I think most
> people set a very high value compared to the TTL.)
>
> --
> Bob Harold
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>


From nobody Mon Sep 11 17:39:40 2017
Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62F1A133233 for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 17:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 53Lg325WmGpn for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 17:39:27 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6092013321F for <dnsop@ietf.org>; Mon, 11 Sep 2017 17:39:27 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id v19so19399723ite.0 for <dnsop@ietf.org>; Mon, 11 Sep 2017 17:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=sOn5Z6Q1vyCyqopDK20ywMf1HIKPGiSAZYqfBPlyk48=; b=FKz6CxlSNrDjQWDkHPubTu4q4kdarQVVElZlHRmWNGzBL3kSVwhe9pvS6gPblWsRg2 1E9Oa517L65kAwZZ/Sdq9hEh9Lfw4gGFwg32+jfWEAFowiewsEs1QPwSvF7M2fX+r8at TtkoztThFYF/mIk3GT34XCC0u8nTE+yAdEEr9Rz3QYOz/WUryuzmyiHW8fl8/S8Y1OQO d+HxuOmwBR8Dqwr6CaE8AsB/l1BaOYQldQEOp1xwYSNAHH1p12UlyUJP1UBjK5b0s1Ra RArjXCq0ervqHfy/OGto3BHjjBYPyYrXffXYffZjBS/jKlE4CLMUNUmvwboGPGtHEFhy kPWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=sOn5Z6Q1vyCyqopDK20ywMf1HIKPGiSAZYqfBPlyk48=; b=EBqESEuCHrPgEW2gdvtu2JXNYle7cZvulkwXj9QN+gu3JJDSOf0ANa0fQY/SDNfxTG 0TOcmWBbOJkeaqXiNm+I1NjrAy/i9pfEBwHq78E+mzNd8NXvFTwElT8sMMR3rqbu+dr0 xGwZxMbDs8fpODB0L48Qmu+cyOYZk0JQ2GER0IxA97pIC68oydUT3BfzgfZ2Tx1QRk4u CkLtTwHP+T9HKIOWEffpYUWMemmqM+5MhqegL2E67pR20dmhEsTloMS0xreCEDq71HzL XokjYbiENDBQLEQUIQttIGkf/X64a6k5B1SEoSmfWnDjC5JMOSNjmDWxNaeM6p/5NQoA hGDw==
X-Gm-Message-State: AHPjjUilGw6UCfjD3xiBi0IUPfHBUyxIgMXf2O5WsfHoY8J/dp+KM/cq eSRzqINFvG5Y+BG71+AXKa4zgqIP48Sg
X-Google-Smtp-Source: AOwi7QAgj61G1apLSIs32zNE7jlGS8Df+H5uX+NEminRdZGUOoeZrLrI093YKouwLMVZlVXBMGyYA6zQi+1PIJcdJDU=
X-Received: by 10.36.214.130 with SMTP id o124mr17567856itg.51.1505176766408;  Mon, 11 Sep 2017 17:39:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.107.71 with HTTP; Mon, 11 Sep 2017 17:39:25 -0700 (PDT)
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Mon, 11 Sep 2017 17:39:25 -0700
Message-ID: <CAH1iCiq_i58S5jNc=BBF1M00WwpxmXHnGjk+8=eH+ukd+zZ5sQ@mail.gmail.com>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114991967c71240558f346d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uly7ZnzD1jdWLSZR9SfKhIwrmfU>
Subject: Re: [DNSOP] opportunistic semi-authoritative caching (Re: DNSOP Call for Adoption - draft-tale-dnsop-serve-stale)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 00:39:38 -0000

--001a114991967c71240558f346d7
Content-Type: text/plain; charset="UTF-8"

>
> Paul wrote:

> Evan Hunt wrote:
> (I do like the idea of advertising a separate expiry value though.)
> i think if we're going to put something into the 20-year deployment funnel
> we should treat the fixed costs as high and demand more benefits. that's
> where the proposal up-thread came from.


The idea is interesting, definitely.

Here's something potentially useful, in terms of "more benefits":

As I understand it, there would be signaling on this via another EDNS bit.

This makes it effectively orthogonal to DNSSEC.

Which means, at least semantically, a response to a query could have
meanings for:

   - The bare RR type
   - The DNSSEC RR type(s) that go with the response to the bare RR query
   - The EXPIRY RR type associated with the base RR query
   - The combination(s) of DNSSEC+EXPIRY RR types

And given the DNSSEC RR types that might appear, the corresponding
DNSSEC+EXPIRY could allow a zone owner to signal a variety of intents.

(Assuming that DNSSEC+EXPIRY records are themselves signed...)
There is the potential for a zone owner to indicate whether an entire zone,
or perhaps some subset of records from the zone, should be treated as
"INSECURE" rather than "INVALID" iff the signature record(s) expire, but
where the DNSKEY used for signing is itself correct.

Or, alternatively, the zone owner could signal that the default behavior is
explicitly correct, i.e. that if for whatever reason, no unexpired
signatures can be obtained, that the result should be treated as
BOGUS/INVALID.

A zone's default EXPIRY could be attached to the SOA record, and the
NSEC/NSEC3 records would be able to securely assert the
existence/non-existence of an EXPIRY for anything in the zone.

Recursives could explicitly determine intent, and pass along the results
(proof) to clients. Clients would not need to guess why INVALID or REFUSED
happens, which would also benefit DNS operators investigating
DNSSEC-related issues.

It is work, but I think it adds a lot of value.

Thoughts?

Brian

--001a114991967c71240558f346d7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote"></blockq=
uote>Paul wrote:<br><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote">Evan =
Hunt wrote:<br>(I do like the idea of advertising a separate expiry value t=
hough.)<br><tt style=3D"color:rgb(0,0,0)">i think if we&#39;re going to put=
 something into the 20-year deployment=C2=A0</tt><tt style=3D"color:rgb(0,0=
,0)">funnel we should treat the fixed costs as high and demand more benefit=
s.=C2=A0</tt><tt style=3D"color:rgb(0,0,0)">that&#39;s where the proposal u=
p-thread came from.</tt>
</blockquote><div><pre style=3D"color:rgb(0,0,0);margin:0em"></pre><pre sty=
le=3D"color:rgb(0,0,0);margin:0em"></pre></div><div><br></div><div>The idea=
 is interesting, definitely.</div><div><br></div><div>Here&#39;s something =
potentially useful, in terms of &quot;more benefits&quot;:</div><div><br></=
div><div>As I understand it, there would be signaling on this via another E=
DNS bit.</div><div><br></div><div>This makes it effectively orthogonal to D=
NSSEC.</div><div><br></div><div>Which means, at least semantically, a respo=
nse to a query could have meanings for:</div><div><ul><li>The bare RR type<=
/li><li>The DNSSEC RR type(s) that go with the response to the bare RR quer=
y</li><li>The EXPIRY RR type associated with the base RR query</li><li>The =
combination(s) of DNSSEC+EXPIRY RR types</li></ul><div>And given the DNSSEC=
 RR types that might appear, the corresponding DNSSEC+EXPIRY could allow a =
zone owner to signal a variety of intents.</div></div><div><br></div><div>(=
Assuming that DNSSEC+EXPIRY records are themselves signed...)</div><div>The=
re is the potential for a zone owner to indicate whether an entire zone, or=
 perhaps some subset of records from the zone, should be treated as &quot;I=
NSECURE&quot; rather than &quot;INVALID&quot; iff the signature record(s) e=
xpire, but where the DNSKEY used for signing is itself correct.</div><div><=
br></div><div>Or, alternatively, the zone owner could signal that the defau=
lt behavior is explicitly correct, i.e. that if for whatever reason, no une=
xpired signatures can be obtained, that the result should be treated as BOG=
US/INVALID.</div><div><br></div><div>A zone&#39;s default EXPIRY could be a=
ttached to the SOA record, and the NSEC/NSEC3 records would be able to secu=
rely assert the existence/non-existence of an EXPIRY for anything in the zo=
ne.</div><div><br></div><div>Recursives could explicitly determine intent, =
and pass along the results (proof) to clients. Clients would not need to gu=
ess why INVALID or REFUSED happens, which would also benefit DNS operators =
investigating DNSSEC-related issues.</div><div><br></div><div>It is work, b=
ut I think it adds a lot of value.</div><div><br></div><div>Thoughts?</div>=
<div><br></div><div>Brian</div></div>

--001a114991967c71240558f346d7--


From nobody Mon Sep 11 22:21:20 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4117A13208E for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 22:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 kklpzzD5RxOF for <dnsop@ietfa.amsl.com>; Mon, 11 Sep 2017 22:21:17 -0700 (PDT)
Received: from mail.hardakers.net (unknown [168.150.236.43]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC801241FC for <dnsop@ietf.org>; Mon, 11 Sep 2017 22:21:17 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id C1B26241F8; Mon, 11 Sep 2017 22:21:16 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "John Levine" <johnl@taugh.com>
Cc: dnsop@ietf.org
References: <20170911013510.17202.qmail@ary.lan>
Date: Mon, 11 Sep 2017 22:21:16 -0700
In-Reply-To: <20170911013510.17202.qmail@ary.lan> (John Levine's message of "11 Sep 2017 01:35:10 -0000")
Message-ID: <yblr2vcxzjn.fsf@w7.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7I7JVgoIHaXxsVEoirPcPb7qM3A>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 05:21:18 -0000

"John Levine" <johnl@taugh.com> writes:

> It seems to me that if someone has enough programming skill to write a
> DNSSEC verifier for her cache or stub resolver, she has enough skill
> to treat localhost as a special case.

I've been trying to figure out for a few days now how to insert my
opinion.  It's kinda like the above but not.  Specifically, we have
multiple naming systems already, and I'd argue that localhost actually
isn't in the DNS naming system.  There is no authoritative source for
it.  In fact, DNSSEC proves this.

Instead, localhost is a operating system convention, a /etc/hosts name,
an NIS name, or one of the other things that is able to resolve that
name.  But the DNS is not where that resolution comes from.

Now, how do we ensure that a conflict never happens?  That's a better
discussion and there are a few options ranging from policy to ensure
it's never assigned, to actually registering it, to...
-- 
Wes Hardaker
USC/ISI


From nobody Tue Sep 12 02:50:52 2017
Return-Path: <abbypan@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2AC213217D for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 02:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mext-hgjk0Jp for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 02:50:50 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC042120724 for <dnsop@ietf.org>; Tue, 12 Sep 2017 02:50:49 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id i189so56547539wmf.1 for <dnsop@ietf.org>; Tue, 12 Sep 2017 02:50:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BOJ65nqo7oaKpQ3y6si231cFV/s+Fir3iAWkLuDfxgQ=; b=TjhBtQgXnr9e2LAPfVERgZiLCUHUR9F2+8oyhv2rCpqH7gArxXxiLqgvcwR76a0pmK 8tNJH3Syfgj6pWvXYD1Smm9nw+TeKk2h6RyhwHcDtGuk6YA554OEn/8gIr+x78J6Ak6S ZM5qafQa75NX8Lz6DT9k01I1Ml/Vxrfk3TREEe6sknFUBNxDfgnuAKiIlOcQEQ8radEs qRU0hDYY5rFLDSovJJ+cxqrpNKcY+uAYDpHyzJOq9vtrpZrz9ep/oY++MSPSkKRsCM7P 5aqJMdfe1ZGAm/HBIoqYKO0TygofKBYzNzVKhIbp7A6NZTuOXnoM9j5MiePP4Tu1u6rN chOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BOJ65nqo7oaKpQ3y6si231cFV/s+Fir3iAWkLuDfxgQ=; b=TP7deSou9xCci2NYHlo2ogPiLnadT6MwI/lUvI9xWeXdB97330e5xhycfSNa0Kt6U6 a6Uj0c9RmbccKJSeSQE8v9jb80EX8KRvreH3CWCzdrI24eVZXEfFbhLyU9yGI9QQ8xNo EIH/XMQ4xLuvcZMG8tNK23SCtfR7dWd52SOYRI+jnAGwkUMpzxaB6Y6g38/QUa2ou3Oa K8FkFNjWak9tEdOF/uU7ilN2r4vCfANQm8t0KC/FYoeRj7DhypxUYkuPHILqgRMt4GuI EO0mGJ+CyfbtFG6JMTUtvglX0K0LDJpT+9o8DuvwFxCqGPgFxYbwE3rq4WxrEIfSXg/i pdtQ==
X-Gm-Message-State: AHPjjUibZotAha3+sddSGfOKYQLcwR6ogKTmVe6vsvxQ/2GsI9JuN4Nr y8+pThWTA/a3Unlp+wPbbSE+k08dLg==
X-Google-Smtp-Source: ADKCNb654kitBdCyUUquZ9v4AcO41FUcd5BAwSEiwR+v6ufaQL0Lpq5BCuurWLPiHRxxYITZ6tLPJT8cd6IMVed0D6k=
X-Received: by 10.80.151.143 with SMTP id e15mr7099596edb.135.1505209848462; Tue, 12 Sep 2017 02:50:48 -0700 (PDT)
MIME-Version: 1.0
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
In-Reply-To: <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
From: Lanlan Pan <abbypan@gmail.com>
Date: Tue, 12 Sep 2017 09:50:37 +0000
Message-ID: <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0dde105481660558fafa4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/twIyJt15pefXABB2BoiAVxv8Krc>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 09:50:52 -0000

--94eb2c0dde105481660558fafa4d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Davey,

ATR make Authoritative Servers send normal big response packet before they
try to send TC response for large RRsets ?

Davey Song <songlinjian@gmail.com>=E4=BA=8E2017=E5=B9=B49=E6=9C=8811=E6=97=
=A5=E5=91=A8=E4=B8=80 =E4=B8=8B=E5=8D=8812:29=E5=86=99=E9=81=93=EF=BC=9A

> Hi folks,
>
> I just submit a draft dealing with issue of large DNS response especially
> in IPv6. Commnets are welcome.
>
> If chairs think it is in the scope of dnsop wg and encourage us to discus=
s
> it in this mailing list, I can submit it as a draft listed in dnsop wg.
>
> Davey
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: 11 September 2017 at 10:13
> Subject: I-D Action: draft-song-atr-large-resp-00.txt
> To: i-d-announce@ietf.org
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : ATR: Additional Truncated Response for Large DN=
S
> Response
>         Author          : Linjian Song
>         Filename        : draft-song-atr-large-resp-00.txt
>         Pages           : 8
>         Date            : 2017-09-10
>
> Abstract:
>    As the increasing use of DNSSEC and IPv6, there are more public
>    evidence and concerns on IPv6 fragmentation issues due to larger DNS
>    payloads over IPv6.  This memo introduces an simple improvement on
>    authoritative server by replying additional truncated response just
>    after the normal large response.
>
>    REMOVE BEFORE PUBLICATION: The source of the document with test
>    script is currently placed at GitHub [ATR-Github].  Comments and pull
>    request are welcome.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-song-atr-large-resp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-song-atr-large-resp-00
> https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft
> <https://www.ietf.org/mailman/listinfo/i-d-announce%0DInternet-Draft>
> directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
--=20
=E8=87=B4=E7=A4=BC  Best Regards

=E6=BD=98=E8=93=9D=E5=85=B0  Pan Lanlan

--94eb2c0dde105481660558fafa4d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Davey,<br><br>ATR make Authoritative Servers send norma=
l big response packet before they try to send TC response for large RRsets =
?<br><div><div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">Davey S=
ong &lt;<a href=3D"mailto:songlinjian@gmail.com">songlinjian@gmail.com</a>&=
gt;=E4=BA=8E2017=E5=B9=B49=E6=9C=8811=E6=97=A5=E5=91=A8=E4=B8=80 =E4=B8=8B=
=E5=8D=8812:29=E5=86=99=E9=81=93=EF=BC=9A<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div dir=3D"ltr"><div>Hi folks,=C2=A0</div><div><br></div><div>I jus=
t submit a draft dealing with issue of large DNS response especially in IPv=
6. Commnets are welcome.=C2=A0</div><div><br></div><div>If chairs think it =
is in the scope of dnsop wg and encourage us to discuss it in this mailing =
list, I can submit it as a draft listed in dnsop wg.</div><div><br></div><d=
iv>Davey</div><div>=C2=A0=C2=A0</div><br><div class=3D"gmail_quote">-------=
--- Forwarded message ----------<br>From: <b class=3D"gmail_sendername"></b=
> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=
=3D"_blank">internet-drafts@ietf.org</a>&gt;</span><br>Date: 11 September 2=
017 at 10:13<br>Subject: I-D Action: draft-song-atr-large-resp-00.txt<br>To=
: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce@i=
etf.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 ATR: Additional Truncated Response for Large DNS Response<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Linj=
ian Song<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-son=
g-atr-large-resp-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 8<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-09-10<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0As the increasing use of DNSSEC and IPv6, there are more publi=
c<br>
=C2=A0 =C2=A0evidence and concerns on IPv6 fragmentation issues due to larg=
er DNS<br>
=C2=A0 =C2=A0payloads over IPv6.=C2=A0 This memo introduces an simple impro=
vement on<br>
=C2=A0 =C2=A0authoritative server by replying additional truncated response=
 just<br>
=C2=A0 =C2=A0after the normal large response.<br>
<br>
=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the document with tes=
t<br>
=C2=A0 =C2=A0script is currently placed at GitHub [ATR-Github].=C2=A0 Comme=
nts and pull<br>
=C2=A0 =C2=A0request are welcome.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-song-atr-large-resp/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-so=
ng-atr-large-resp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-song-atr-large-resp-00" rel=3D=
"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-song-atr-l=
arge-resp-00</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-=
00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/h=
tml/draft-song-atr-large-resp-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announce@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce%0DInternet-Dr=
aft" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shadow.html</a><b=
r>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel=3D"noreferrer"=
 target=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
</div><br></div>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
</blockquote></div></div></div></div></div><div dir=3D"ltr">-- <br></div><d=
iv class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D=
"ltr">=E8=87=B4=E7=A4=BC=C2=A0 Best Regards<br><br>=E6=BD=98=E8=93=9D=E5=85=
=B0=C2=A0 Pan Lanlan<br></div></div>

--94eb2c0dde105481660558fafa4d--


From nobody Tue Sep 12 03:41:39 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C10E1333A8 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 03:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 djpjz6ABe_XW for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 03:41:35 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33E0313339D for <dnsop@ietf.org>; Tue, 12 Sep 2017 03:41:35 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:59020) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dridE-0000gI-3A (Exim 4.89) (return-path <dot@dotat.at>); Tue, 12 Sep 2017 11:41:29 +0100
Date: Tue, 12 Sep 2017 11:41:28 +0100
From: Tony Finch <dot@dotat.at>
To: Wes Hardaker <wjhns1@hardakers.net>
cc: John Levine <johnl@taugh.com>, dnsop@ietf.org
In-Reply-To: <yblr2vcxzjn.fsf@w7.hardakers.net>
Message-ID: <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sK_ni1gEZ6CXQ7pVNjpZFfysBP4>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 10:41:37 -0000

Wes Hardaker <wjhns1@hardakers.net> wrote:
>
> Specifically, we have multiple naming systems already, and I'd argue
> that localhost actually isn't in the DNS naming system.  There is no
> authoritative source for it.  In fact, DNSSEC proves this.
>
> Instead, localhost is a operating system convention, a /etc/hosts name,
> an NIS name, or one of the other things that is able to resolve that
> name.  But the DNS is not where that resolution comes from.

I think this makes sense, but it isn't the whole story. From my brief look
at a small amount of traffic, localhost queries are basically all handled
inside the stub, so it is de facto as you describe. But it has long been
the case that DNS servers are also supposed to handle localhost, e.g.

RFC 1537 section 10
RFC 1912 section 4.1
RFC 2606 section 2
RFC 6761 section 6.3

However, implementations differ - BIND requires explicit configuration,
Unbound handles localhost by default.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
South Utsire, Forties, Cromarty, Forth: Westerly 5 or 6, becoming variable 3
or 4, then northerly or northeasterly 5 or 6, occasionally 7 in Forties.
Moderate occasionally rough in Forties. Rain. Good occasionally poor.


From nobody Tue Sep 12 07:06:41 2017
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1340132D43 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 07:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 l1c6gWaKf1hS for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 07:06:33 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 478D41326DF for <dnsop@ietf.org>; Tue, 12 Sep 2017 07:06:33 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id 846606A3C4; Tue, 12 Sep 2017 16:06:31 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id E2A296A3C3; Tue, 12 Sep 2017 16:06:28 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59b7e9e4-034f-7f000001272a-7f000001dec7-1 for <multiple-recipients>; Tue, 12 Sep 2017 16:06:28 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id 924A76A267; Tue, 12 Sep 2017 16:06:28 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id 867743C10D4; Tue, 12 Sep 2017 16:06:28 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cqvOEBO9Y8jV; Tue, 12 Sep 2017 16:06:28 +0200 (CEST)
Received: from [192.168.0.20] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 6900B3C007B; Tue, 12 Sep 2017 16:06:28 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop <dnsop@ietf.org>
Date: Tue, 12 Sep 2017 16:06:51 +0200
Message-ID: <63DA2E77-8507-4F25-8684-14EABF9A530E@powerdns.com>
In-Reply-To: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.7r5412)
X-purgate-ID: 151428::1505225188-0000034F-C5908ED7/0/0
X-purgate-type: clean
X-purgate-size: 1379
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Yij2_grdrpd_O_B3F_cA2cLcSUY>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 14:06:38 -0000

Hello,

On 6 Sep 2017, at 16:00, tjw ietf wrote:

> When the idea of having a Call for Adoption for this document came up, =

> we
> thought long and hard about this one.  However, the comments from the
> working group focused this document to address the specific issue of =

> the
> local hostname.
>
> This starts a formal Call for Adoption for
> draft-west-let-localhost-be-localhost
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/=


I support adoption of this draft.

I would also like to take this opportunity to codify a related best =

operational practice. As Tony Finch mentioned elsewhere in the thread =

(linking to =

http://news.uis.cam.ac.uk/articles/2017/09/01/deleting-localhost-entries-=
from-the-cam-ac-uk-dns-zone), =

having a localhost entry in any zone file is an insecure practice.

Since we are doing a draft/RFC on what localhost is and is not, I =

suggest we put some text in there banning (MUST NOT) the practice of =

having localhost entries (at least those pointing to 127.0.0.1/::1?) in =

auth zones. If there is agreement on this I am happy to contribute text. =

This may mean having to say we are updating RFC 1912.

I am happy to review in any case.

Kind regards,
-- =

Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Tue Sep 12 08:04:24 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11501133073 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 sLpp38QRzWae for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:04:21 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 217EF132335 for <dnsop@ietf.org>; Tue, 12 Sep 2017 08:04:21 -0700 (PDT)
Received: from [192.168.16.67] (wsip-70-184-101-190.ph.ph.cox.net [70.184.101.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 62AC561FA2; Tue, 12 Sep 2017 15:04:19 +0000 (UTC)
Message-ID: <59B7F771.5020607@redbarn.org>
Date: Tue, 12 Sep 2017 08:04:17 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: Wes Hardaker <wjhns1@hardakers.net>, dnsop@ietf.org,  John Levine <johnl@taugh.com>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hN1MsfXRdVi59dMH4jD6MsZxllc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 15:04:23 -0000

Tony Finch wrote:
> Wes Hardaker<wjhns1@hardakers.net>  wrote:
>> Instead, localhost is a operating system convention, a /etc/hosts name,
>> an NIS name, or one of the other things that is able to resolve that
>> name.  But the DNS is not where that resolution comes from.
>
> I think this makes sense, but it isn't the whole story. From my brief look
> at a small amount of traffic, localhost queries are basically all handled
> inside the stub, so it is de facto as you describe. But it has long been
> the case that DNS servers are also supposed to handle localhost, e.g.
>
> RFC 1537 section 10
> RFC 1912 section 4.1
> RFC 2606 section 2
> RFC 6761 section 6.3
>
> However, implementations differ - BIND requires explicit configuration,
> Unbound handles localhost by default.

while i've generally included a localhost.$ORIGIN A RR in zones that 
appear in my stub resolver search lists, in order that "localhost" be 
found, i believe that the host name lookup library which calls and/or 
depends upon, among other things, a DNS stub resolver, ought to handle 
the "localhost" convention. and indeed, most of these lookup libraries 
have a concept similar to "/etc/hosts" today, where "localhost" lives.

no standards-track RFC currently requires that "localhost" return NXD, 
to make explicit that it's the host name lookup library "SHOULD", and 
that the DNS "SHOULD NOT", handle this name to address translation. we 
didn't used to standardized behaviour that was not seen "on the wire" 
simply because interoperability testing would be hard to imagine. and i 
don't imagine i'll have my "localhost.$ORIGIN" RR's out of any zones.

-- 
P Vixie


From nobody Tue Sep 12 08:07:04 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2951341FB for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 6R8CiPsLot-P for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:07:01 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97676132192 for <dnsop@ietf.org>; Tue, 12 Sep 2017 08:07:01 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id ADA7C280D76; Tue, 12 Sep 2017 17:06:59 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id A7B1A280D7C; Tue, 12 Sep 2017 17:06:59 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id A1497280D76; Tue, 12 Sep 2017 17:06:59 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 9E90F6423536; Tue, 12 Sep 2017 17:06:59 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 97066407E1; Tue, 12 Sep 2017 17:06:59 +0200 (CEST)
Date: Tue, 12 Sep 2017 17:06:59 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Lanlan Pan <abbypan@gmail.com>
Cc: Davey Song <songlinjian@gmail.com>, dnsop <dnsop@ietf.org>
Message-ID: <20170912150659.vub6yf6e25nup775@nic.fr>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.12.145716
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9mH4eixkDOf7FvrBN6AJpi90RBQ>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 15:07:03 -0000

On Tue, Sep 12, 2017 at 09:50:37AM +0000,
 Lanlan Pan <abbypan@gmail.com> wrote 
 a message of 210 lines which said:

> ATR make Authoritative Servers send normal big response packet
> before they try to send TC response for large RRsets ?

Yes, section 3. "it is suggested a timer to delay the second truncated
response to around 10 millisecond which can be configured by local
operation". (In the spirit of RFC 6555.)


From nobody Tue Sep 12 08:14:34 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57920133025 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 0Fu4crRmGQsV for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:14:32 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81E3C132192 for <dnsop@ietf.org>; Tue, 12 Sep 2017 08:14:32 -0700 (PDT)
Received: from [192.168.16.67] (wsip-70-184-101-190.ph.ph.cox.net [70.184.101.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 3149B61FA2; Tue, 12 Sep 2017 15:14:32 +0000 (UTC)
Message-ID: <59B7F9D6.50900@redbarn.org>
Date: Tue, 12 Sep 2017 08:14:30 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: Lanlan Pan <abbypan@gmail.com>, Davey Song <songlinjian@gmail.com>,  dnsop <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com> <20170912150659.vub6yf6e25nup775@nic.fr>
In-Reply-To: <20170912150659.vub6yf6e25nup775@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/I0kTVkFaLRD-csaqtuYV__6wiTs>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 15:14:33 -0000

Stephane Bortzmeyer wrote:
> On Tue, Sep 12, 2017 at 09:50:37AM +0000,
>   Lanlan Pan<abbypan@gmail.com>  wrote
>   a message of 210 lines which said:
>
>> ATR make Authoritative Servers send normal big response packet
>> before they try to send TC response for large RRsets ?
>
> Yes, section 3. "it is suggested a timer to delay the second truncated
> response to around 10 millisecond which can be configured by local
> operation". (In the spirit of RFC 6555.)

noting, 10ms isn't enough. packet reordering due to multipath load 
balancing has been observed as high as 60ms due to "buffer bloat".

-- 
P Vixie


From nobody Tue Sep 12 08:54:34 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4F2132D48 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 zAXhDwR13bcD for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 08:54:30 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95A151320D9 for <dnsop@ietf.org>; Tue, 12 Sep 2017 08:54:30 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:38518) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1drnW5-000prT-2D (Exim 4.89) (return-path <dot@dotat.at>); Tue, 12 Sep 2017 16:54:25 +0100
Date: Tue, 12 Sep 2017 16:54:25 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Vixie <paul@redbarn.org>
cc: dnsop@ietf.org, John Levine <johnl@taugh.com>,  Wes Hardaker <wjhns1@hardakers.net>
In-Reply-To: <59B7F771.5020607@redbarn.org>
Message-ID: <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/f3nKca21OfoyPrPJKjWOr5ldMu0>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 15:54:32 -0000

Paul Vixie <paul@redbarn.org> wrote:
>
> while i've generally included a localhost.$ORIGIN A RR in zones that appear in
> my stub resolver search lists, in order that "localhost" be found,

I agree with the rest of your message but I want to highlight this bit
because it is directly related to the main reason this draft exists.

Your localhost records (like the ones I deleted from cam.ac.uk last week)
are troublesome for the web browser same origin security policy: they can
lead to vulnerabilites when your websites are accessed from multi-user
machines and in other more obscure circumstances - for details, see
http://seclists.org/bugtraq/2008/Jan/270

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Tyne, Dogger: Westerly backing southeastrly 4 or 5, occasionally 6 at first,
then becoming cyclonic, mainly northwesterly later, 6 to gale 8, occasionally
severe gale 9 later in south. Moderate or rough, occasionally very rough later
in south. Rain. Good occasionally poor.


From nobody Tue Sep 12 09:54:10 2017
Return-Path: <vjs@rhyolite.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2B4013308F for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 09:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 cBQ3FJya7DHq for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 09:54:05 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite-v6.rhyolite.com [IPv6:2001:470:4b:581::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B03EA132403 for <dnsop@ietf.org>; Tue, 12 Sep 2017 09:54:05 -0700 (PDT)
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.15.2/8.15.2) with ESMTPS id v8CGrmQ9089849 (CN=www.rhyolite.com version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <dnsop@ietf.org> env-from <vjs@rhyolite.com>; Tue, 12 Sep 2017 16:53:48 GMT
Received: (from vjs@localhost) by calcite.rhyolite.com (8.15.2/8.15.2/Submit) id v8CGrmr4089848 for dnsop@ietf.org; Tue, 12 Sep 2017 16:53:48 GMT
Date: Tue, 12 Sep 2017 16:53:48 GMT
From: Vernon Schryver <vjs@rhyolite.com>
Message-Id: <201709121653.v8CGrmr4089848@calcite.rhyolite.com>
To: dnsop@ietf.org
In-Reply-To: <59B7F9D6.50900@redbarn.org>
X-DCC-Rhyolite-Metrics: calcite.rhyolite.com; whitelist
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HKjHE8wEOqUqS8oFFW500XG0jdc>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 16:54:08 -0000

> From: Paul Vixie <paul@redbarn.org>
> To: Stephane Bortzmeyer <bortzmeyer@nic.fr>

> > Yes, section 3. "it is suggested a timer to delay the second truncated
> > response to around 10 millisecond which can be configured by local
> > operation". (In the spirit of RFC 6555.)
>
> noting, 10ms isn't enough. packet reordering due to multipath load 
> balancing has been observed as high as 60ms due to "buffer bloat".

I've fought consistent 5 second delays from 'buffer bloat', albeit
20+ years ago at 56K and T1 speeds with Cisco routers on a private IP
world wide network.  A route change in the midst of such delays, whether
from load balancing or anything else, would re-order packets unless
they are delayed by the worst case buffering delay.
We've probably all also seen other cases where an individual IP packet
in a stream (e.g. ICMP/IP) has been or or less mysteriously delayed
by seconds.

At the other extreme, if 10 or 60 ms is good enough in late 2017, might
it be too conservative in 2027?

In other words, it sounds undesirable to write such constants into
any standard unless absolutely necessary.

The delays in section 5.5 of RFC 6555 seem to differ.  They are at
least as much about what humans notice ("humn factors" in RFC 6555)
as network delays; 150-250 ms is about the threshold for what people
consider "sluggish."  150-250 ms also is vastly longer than 10 ms., and
long compared to network delays even in 2012.


Vernon Schryver    vjs@rhyolite.com


From nobody Tue Sep 12 10:04:48 2017
Return-Path: <rlb@ipv.sx>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C67132EC1 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 10:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 DCZv5epVqGdb for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 10:04:46 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9435132D79 for <dnsop@ietf.org>; Tue, 12 Sep 2017 10:04:45 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id 108so24106099wra.5 for <dnsop@ietf.org>; Tue, 12 Sep 2017 10:04:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lhaXzl9PHExR4t5cBrHiKhiGmgVZQJhWpXiIR3qLf48=; b=c7ojVn89NV/YQPXDAd+C5Ep1fztyjF1dvvvOukJBW6dbO8hEJE5HlpNsRf8hxnhkuI 5ap1PoG5Mwu2mnuClwHLrgiJClP32SZCCj2yyLUdR4VIZxCul7mzSPWJwLB1Lb/qY7Vm GmupPc7v6TRtedG+Bnrm46jIEBNVvrcbUtwA/iZ7kkreZxY5iqKlH0zADci3YJ+3A1Og ZdRjTUiafLRMu64P+FF7IyJV3GkUGUwOeCh0OungTo8LTLu6VDviYzk3lVzpUaSgLCWi VLWsVsc1+h7POO7M7pJNSPHyZffQQYzvhvaWfgtfZsNpD1Ld/vFSVMGWBOb24v7kMuaC NySA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lhaXzl9PHExR4t5cBrHiKhiGmgVZQJhWpXiIR3qLf48=; b=bHm+X5CANinW+F41swjJ8bM/m24yrdoXeoVJaOseIoM7KUxMvSOse4GlxELySl19ub 7MMDOCXAf0X42Mbwful1JEY3vFrZTeQU/8eWz4vvMAW3y8uLt7UqFhpoh/LTwXvHxyGd nKopckIM4JUMVkIR96soQq1/qratab5ptPVFAj4kXmhgWNcaB2X+4N2lEK9yjXf8KLG1 UZjjeCvmTzHve8VNTg3T4IvGCcJum5X1pnjj/+8KCIwLewVRTXJsgY14NgFDZtnDV+MP ewdnYI8acX70/HqpVsRzimpbGVr6axMScMlDKiit5zVEfp0pVCflJP7PHz1AuF2hquCo 7KJQ==
X-Gm-Message-State: AHPjjUgY/69GM6C+ZtZjiOBtZb8lc0ihNoXqgAWYegbGiiTt39yp4ULQ 6kmscZKHdJao58vkYh4YBLfAQBRdjmHIIiQR8A==
X-Google-Smtp-Source: ADKCNb6Hxg9zYf0FaH0ERZDqjJWLv5x2eGc+qr/Lm8ky5UTWAh9LkZj9w+6tHZFsFyB+BY8lcRECSFztp//BvRve+fM=
X-Received: by 10.223.161.194 with SMTP id v2mr13554396wrv.45.1505235884187; Tue, 12 Sep 2017 10:04:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.159.200 with HTTP; Tue, 12 Sep 2017 10:04:43 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
From: Richard Barnes <rlb@ipv.sx>
Date: Tue, 12 Sep 2017 10:04:43 -0700
Message-ID: <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, John Levine <johnl@taugh.com>, Wes Hardaker <wjhns1@hardakers.net>
Content-Type: multipart/alternative; boundary="f403045f2ed62ea4d90559010a26"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vEcnkW5jTgvqhdSB68Xh9sPCdpI>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 17:04:48 -0000

--f403045f2ed62ea4d90559010a26
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 12, 2017 at 8:54 AM, Tony Finch <dot@dotat.at> wrote:

> Paul Vixie <paul@redbarn.org> wrote:
> >
> > while i've generally included a localhost.$ORIGIN A RR in zones that
> appear in
> > my stub resolver search lists, in order that "localhost" be found,
>
> I agree with the rest of your message but I want to highlight this bit
> because it is directly related to the main reason this draft exists.
>
> Your localhost records (like the ones I deleted from cam.ac.uk last week)
> are troublesome for the web browser same origin security policy: they can
> lead to vulnerabilites when your websites are accessed from multi-user
> machines and in other more obscure circumstances - for details, see
> http://seclists.org/bugtraq/2008/Jan/270


Cf.
https://tools.ietf.org/html/draft-thomson-postel-was-wrong-00#section-4.1

When something shouldn't work, it shouldn't work.

--Richard



>
>
> Tony.
> --
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h
> punycode
> Tyne, Dogger: Westerly backing southeastrly 4 or 5, occasionally 6 at
> first,
> then becoming cyclonic, mainly northwesterly later, 6 to gale 8,
> occasionally
> severe gale 9 later in south. Moderate or rough, occasionally very rough
> later
> in south. Rain. Good occasionally poor.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--f403045f2ed62ea4d90559010a26
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Sep 12, 2017 at 8:54 AM, Tony Finch <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dot@dotat.at" target=3D"_blank">dot@dotat.at</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gm=
ail-">Paul Vixie &lt;<a href=3D"mailto:paul@redbarn.org">paul@redbarn.org</=
a>&gt; wrote:<br>
&gt;<br>
&gt; while i&#39;ve generally included a localhost.$ORIGIN A RR in zones th=
at appear in<br>
&gt; my stub resolver search lists, in order that &quot;localhost&quot; be =
found,<br>
<br>
</span>I agree with the rest of your message but I want to highlight this b=
it<br>
because it is directly related to the main reason this draft exists.<br>
<br>
Your localhost records (like the ones I deleted from <a href=3D"http://cam.=
ac.uk" rel=3D"noreferrer" target=3D"_blank">cam.ac.uk</a> last week)<br>
are troublesome for the web browser same origin security policy: they can<b=
r>
lead to vulnerabilites when your websites are accessed from multi-user<br>
machines and in other more obscure circumstances - for details, see<br>
<a href=3D"http://seclists.org/bugtraq/2008/Jan/270" rel=3D"noreferrer" tar=
get=3D"_blank">http://seclists.org/bugtraq/<wbr>2008/Jan/270</a></blockquot=
e><div><br></div><div>Cf. <a href=3D"https://tools.ietf.org/html/draft-thom=
son-postel-was-wrong-00#section-4.1">https://tools.ietf.org/html/draft-thom=
son-postel-was-wrong-00#section-4.1</a></div><div><br></div><div>When somet=
hing shouldn&#39;t work, it shouldn&#39;t work.<br></div><div><br></div><di=
v>--Richard<br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><br>
<span class=3D"gmail-"><br>
Tony.<br>
--<br>
f.anthony.n.finch=C2=A0 &lt;<a href=3D"mailto:dot@dotat.at">dot@dotat.at</a=
>&gt;=C2=A0 <a href=3D"http://dotat.at/" rel=3D"noreferrer" target=3D"_blan=
k">http://dotat.at/</a>=C2=A0 -=C2=A0 I xn--zr8h punycode<br>
</span>Tyne, Dogger: Westerly backing southeastrly 4 or 5, occasionally 6 a=
t first,<br>
then becoming cyclonic, mainly northwesterly later, 6 to gale 8, occasional=
ly<br>
severe gale 9 later in south. Moderate or rough, occasionally very rough la=
ter<br>
in south. Rain. Good occasionally poor.<br>
<div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
</div></div></blockquote></div><br></div></div>

--f403045f2ed62ea4d90559010a26--


From nobody Tue Sep 12 10:11:38 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C7A133096 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 10:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=n69m22xv; dkim=pass (1536-bit key) header.d=taugh.com header.b=HXR7y6TK
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 O4jrdGRSFbJP for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 10:11:35 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA2F133095 for <dnsop@ietf.org>; Tue, 12 Sep 2017 10:11:35 -0700 (PDT)
Received: (qmail 17831 invoked from network); 12 Sep 2017 17:11:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=45a4.59b81545.k1709; bh=A7RB2sL/n0avAgpef16DGFDmTf5YVbHL30LHqvv37Hc=; b=n69m22xvv5ePbQKCu/mwavjEBw+WLu7plPBLgpxtJYTSPn7GKZcMKUf/j8UrWWxyIU/DLL1x2a2gQruSP0bRjctx66x4dffGWWezhtPIKfpf+/0j+Dr7CnQVT4sUgHm76vRFJEWLVo94RQXnItc52PuwAIJbsB8onRak3AZNMbybdwjRUqcYEJ9UAtaOZ3cFg5DnCrJZ13gUkZ0NooIWSMASA3TdKH9GtWe6b491RoO844UsvciN7z1X1SFzXpMr
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=45a4.59b81545.k1709; bh=A7RB2sL/n0avAgpef16DGFDmTf5YVbHL30LHqvv37Hc=; b=HXR7y6TKMdPTNYD/LdPys4Ov/H7TKepwFiTlabKty458AUeYj/8wr7IQ6GOMnQ71CqiDcWVePFCJoCG66XJHCBt0IGZUv5V/i/3ForhtApZQ13k/l7TZIr7BOuQVqiSt+w3HGmLpXFP+ck1bvftfW5hcXopxZyxLca1dukt4KOM8IBIZGFH0+0dZ6P59eLjbraLG3YV44Fg17YHruNZ5MHzvtLpFU/GkOh3YC2YeLse4gKZKVDskI5eaplY3NT+Z
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 12 Sep 2017 17:11:33 -0000
Date: 12 Sep 2017 13:11:32 -0400
Message-ID: <alpine.OSX.2.21.1709121310230.1058@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Richard Barnes" <rlb@ipv.sx>
Cc: "dnsop" <dnsop@ietf.org>
In-Reply-To: <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk> <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r1jmNwWezYoDUTgDWyNHs101zp8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 17:11:37 -0000

> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-00#section-4.1
>
> When something shouldn't work, it shouldn't work.

I agree but this is a tangent.  The draft is about localhost. or maybe 
<something>.localhost.  It's not about localhost.<something>.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Tue Sep 12 12:08:39 2017
Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC45132D91 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 12:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 mMw4Gu_y2l1y for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 12:08:37 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310E513293A for <dnsop@ietf.org>; Tue, 12 Sep 2017 12:08:37 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id o200so996499itg.0 for <dnsop@ietf.org>; Tue, 12 Sep 2017 12:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oQUqUd9NKomt3AvSDg1Jj7txdXwIy5R9sMmxdrXEuv8=; b=Q4nWSylEVJjRBY9gAQF4NAeHcQQZJI9WE8TNBPDnqtfs7vzG/BmuzJbyhEuKw7gObD aO+EubKrLWotKsFwsJlkmT0EfaLtSfpXFE21xUV++Fk6IewVOE0JTw6LOmIGVH8q+m+M iDPvTeHr0bzKr2a63zAsovB4UiDsl2HiO3Tds=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oQUqUd9NKomt3AvSDg1Jj7txdXwIy5R9sMmxdrXEuv8=; b=NDP0WtM5XaStMgxCmZaPZaMBNagwjcvDB1ZsUUkkvBw0mqM9wKo8nwGYX1Af/Q2Cqt fAupv0v4R6X54xFqLh3ZV/9mPPur9jLJclGtoqbf+D+mqxo6lrif6IDgEuZhMXEQ5xXb Yl+miR0UfE6kA9ugaOjlbnHJ3e86N4Uqkjn2x+qcqjmr8uMFs0nNvrtoiEGZwrgIARTC 9jg4U7ePh9L9orzSKFAvukhDfE5i9Xbia89AHiwkhVMCtTBBMLQslKeQ8CVRwrldyZn+ 6QwF+l8Lk+jyrjMGjLAEcbt/Z+LVM04hHcBBqAXvq9AHVRrVmVP1UdYLNvwGd6lpSmUn 0tLA==
X-Gm-Message-State: AHPjjUiibLlExKnMQniEC+FrCiTNZkhKpKwWKigxM32xJyXsIYsWA1YI y4oRg3kUfnhhPXpV0jOy+wVc8/WZ5cQ=
X-Google-Smtp-Source: AOwi7QCYNMk10/pjhspu5e3MVGVZQ5Lk5nkZI7ixOZJ3yEfUDdkl+8EqlvGtlqF5Js8AkutmLonNtQ==
X-Received: by 10.36.9.206 with SMTP id 197mr869717itm.77.1505243316616; Tue, 12 Sep 2017 12:08:36 -0700 (PDT)
Received: from node-131fefo2fem9ketych.ipv6.teksavvy.com (node-131fefo2fem9ketych.ipv6.teksavvy.com. [2607:f2c0:101:202:e471:bd3f:722c:121]) by smtp.gmail.com with ESMTPSA id 126sm6680143itw.41.2017.09.12.12.08.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Sep 2017 12:08:34 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.OSX.2.21.1709121310230.1058@ary.qy>
Date: Tue, 12 Sep 2017 15:08:33 -0400
Cc: Richard Barnes <rlb@ipv.sx>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B71B0CD-FAE3-4F6F-B10A-97D00300B03D@hopcount.ca>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk> <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com> <alpine.OSX.2.21.1709121310230.1058@ary.qy>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IfBpsDlU3jsN2SQJotAxmBkp3sA>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 19:08:38 -0000

On 12 Sep 2017, at 13:11, John R Levine <johnl@taugh.com> wrote:

>> =
https://tools.ietf.org/html/draft-thomson-postel-was-wrong-00#section-4.1
>>=20
>> When something shouldn't work, it shouldn't work.
>=20
> I agree but this is a tangent.  The draft is about localhost. or maybe =
<something>.localhost.  It's not about localhost.<something>.

The problem with this clarification is that in practice "localhost." is =
almost always spelt "localhost".


Joe=


From nobody Tue Sep 12 12:40:41 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A00F132ECE for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 12:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=EUwRL0kg; dkim=pass (1536-bit key) header.d=taugh.com header.b=I75rAwaG
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 bRuM87ucvAaw for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 12:40:38 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB07013293A for <dnsop@ietf.org>; Tue, 12 Sep 2017 12:40:37 -0700 (PDT)
Received: (qmail 88390 invoked from network); 12 Sep 2017 19:40:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=15941.59b83834.k1709; bh=KQV7/kL920CCedmn0I18YlmuOgiMTr1HgKA0t1CrxE0=; b=EUwRL0kgWcAmZUHO2PZd42UKa9ifN7XTaYCnZF/vRlzadk/x1aVytyV7eeQFU5L+V15ArOWDA5xp4wK6L/QLoc7qsnd0AjsVkcvHvrn3802HtrRmm3ArIvMwt0bzuihMheqite+nfp9877zv4kEVmWgMkAelI42dGMPF9Rw755yQb9jbeiDjilylfEPMcM7tBZ4rrhapsqiZUsZg5zCNEQZP3XAYhe1hKZ5JOMRtFZpssRRzDWyh38N3wLpsVenK
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=15941.59b83834.k1709; bh=KQV7/kL920CCedmn0I18YlmuOgiMTr1HgKA0t1CrxE0=; b=I75rAwaGpv47qFp8afl6JGO00rfU9P5YDQPXwcfyHb64VIQho97qh96V69ttjv2/K7daL/obB44f3JgIqJr0miQXqA77xyqvMAf70tI8h5wth3U4tK5+8zBHtd8iie/ZoU2ioueXjjk0VIgJhIG5Fmhr7vK3t85tch2dVQi4DylAahHoJzQJHUfmw2O0ZJo0uTaxiK6HAa0hoWFe8Wc2UIfz3P97WDHpCo0G2ytX4rs6ZqD4B8JGFiHX2dDMdPFA
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 12 Sep 2017 19:40:36 -0000
Date: 12 Sep 2017 15:40:35 -0400
Message-ID: <alpine.OSX.2.21.1709121536140.1747@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Joe Abley" <jabley@hopcount.ca>
Cc: "dnsop" <dnsop@ietf.org>
In-Reply-To: <9B71B0CD-FAE3-4F6F-B10A-97D00300B03D@hopcount.ca>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk> <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com> <alpine.OSX.2.21.1709121310230.1058@ary.qy> <9B71B0CD-FAE3-4F6F-B10A-97D00300B03D@hopcount.ca>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kqkbH3ZSdfy1vgOR07DCRd5hPaI>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 19:40:39 -0000

>>> When something shouldn't work, it shouldn't work.
>>
>> I agree but this is a tangent.  The draft is about localhost. or maybe <something>.localhost.  It's not about localhost.<something>.
>
> The problem with this clarification is that in practice "localhost." is almost always spelt "localhost".

Well, OK, but I hope we can limit the advice to tne meaning of localhost 
as a TLD-ish name, and not rehash the well known problems with search 
lists.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Tue Sep 12 13:31:29 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC041330CA for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 13:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 q3fpflOfdp7V for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 13:31:26 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09E641330C9 for <dnsop@ietf.org>; Tue, 12 Sep 2017 13:31:26 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 250D434BF31; Tue, 12 Sep 2017 20:30:55 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 0EDB916005C; Tue, 12 Sep 2017 20:30:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DB1F9160076; Tue, 12 Sep 2017 20:30:54 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id loy42u5elcHe; Tue, 12 Sep 2017 20:30:54 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 91A2416005C; Tue, 12 Sep 2017 20:30:54 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 83859851E1DB; Wed, 13 Sep 2017 06:30:53 +1000 (AEST)
To: "John R Levine" <johnl@taugh.com>
Cc: "Joe Abley" <jabley@hopcount.ca>, dnsop <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk> <CAL02cgRj6R8hRUP810+eDdGVg1VovFYHAq_fA6uqiLAYdmt3LQ@mail.gmail.com> <alpine.OSX.2.21.1709121310230.1058@ary.qy> <9B71B0CD-FAE3-4F6F-B10A-97D00300B03D@hopcount.ca> <alpine.OSX.2.21.1709121536140.1747@ary.qy>
In-reply-to: Your message of "12 Sep 2017 15:40:35 -0400." <alpine.OSX.2.21.1709121536140.1747@ary.qy>
Date: Wed, 13 Sep 2017 06:30:53 +1000
Message-Id: <20170912203053.83859851E1DB@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dWODUOG5WLiHCMWihuE7hZyQhe8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 20:31:28 -0000

In message <alpine.OSX.2.21.1709121536140.1747@ary.qy>, "John R Levine" writes:
> >>> When something shouldn't work, it shouldn't work.
> >>
> >> I agree but this is a tangent.  The draft is about localhost. or maybe <so
> mething>.localhost.  It's not about localhost.<something>.
> >
> > The problem with this clarification is that in practice "localhost." is alm
> ost always spelt "localhost".
> 
> Well, OK, but I hope we can limit the advice to tne meaning of localhost 
> as a TLD-ish name, and not rehash the well known problems with search 
> lists.

Unfortunately they are all related.  "localhost" as a single label
gets the search list applied, then is tried as is.  "_foo._tcp.localhost"
as a multi-label string gets tried as is then the search list is
applied.  localhost is the one pre-hierachical hostname that we still
use.  Other single label hostnames are intended to be short cuts to
a heirachical hostnames.

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Sep 12 15:21:08 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C89E132F5D for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 15:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 iIYDFoEQ-J-E for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 15:21:05 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52F3212421A for <dnsop@ietf.org>; Tue, 12 Sep 2017 15:21:05 -0700 (PDT)
Received: (qmail 49007 invoked by uid 125); 12 Sep 2017 22:21:04 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 12 Sep 2017 22:21:04 -0000
Date: 12 Sep 2017 22:17:38 -0000
Message-ID: <20170912221738.1645.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CAHw9_iJL-Lc84GnMtOERM2oupVrMxKjoYGeumE9K77RwOE4uqQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PVDT4JAeB7vB3aPfc3Xz_NrC0L0>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 22:21:06 -0000

In article <CAHw9_iJL-Lc84GnMtOERM2oupVrMxKjoYGeumE9K77RwOE4uqQ@mail.gmail.com> you write:
>I think that this boils down to: It is an error to send a query for
>localhost (or anything under localhost) to the DNS. The main reason
>for this (at least from my reading of the thread) is a security
>argument -- you want to be completely sure that 'localhost' will
>always be 127.0.0.1 / ::1 / some local equivalent, and this is not a
>guarantee we can expect from the DNS[0]. Because of this it is better
>the have queries that accidentally *do* leak into the DNS get a
>failure (NXDOMAIN) - this avoids having (security important) cases
>work fine until there is an attacker.
>
>Is this a reasonable summary? Perhaps once we agree if *is* the
>behavior we want we'll have an easier time deciding exactly how...

Sounds right to me.

With respect to Tim's suggestion that we invent
localhost-we-really-mean-it-this-time, the existing localhost isn't
going away, and it is my impression that more often than not software
already does what this draft suggests.

R's,
John


From nobody Tue Sep 12 15:42:28 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A74B2132F78 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 15:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 PAdi0p6IIq_L for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 15:42:25 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73B6A132331 for <dnsop@ietf.org>; Tue, 12 Sep 2017 15:42:25 -0700 (PDT)
Received: from [100.72.16.2] (ip67-155-240-118.z240-155-67.customer.algx.net [67.155.240.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 2263061FA2; Tue, 12 Sep 2017 22:42:25 +0000 (UTC)
Message-ID: <59B862D0.5010203@redbarn.org>
Date: Tue, 12 Sep 2017 15:42:24 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
CC: dnsop@ietf.org, John Levine <johnl@taugh.com>,  Wes Hardaker <wjhns1@hardakers.net>
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yIIONY1-5ly1fwrRDMnu3PZNvOs>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 22:42:27 -0000

Tony Finch wrote:
> Paul Vixie<paul@redbarn.org>  wrote:
> > ...
> Your localhost records (like the ones I deleted from cam.ac.uk last week)
> are troublesome for the web browser same origin security policy: they can
> lead to vulnerabilites when your websites are accessed from multi-user
> machines and in other more obscure circumstances - for details, see
> http://seclists.org/bugtraq/2008/Jan/270

huh. this web thing really wasn't any better thought out than this 
internet thing, was it? (same-origin, as a security policy, reeks of 
n00bism, even without this localhost defect.)

thanks for the heads-up. maybe i will delete it after all.

-- 
P Vixie


From nobody Tue Sep 12 16:25:08 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1879C132F6E; Tue, 12 Sep 2017 16:25:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150525870106.30485.18179687243292311597@ietfa.amsl.com>
Date: Tue, 12 Sep 2017 16:25:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tTM8ZVAidGyzd_kyQTTiVA-11Po>
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 23:25:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

        Title           : Security Considerations for RFC5011 Publishers
        Authors         : Wes Hardaker
                          Warren Kumari
	Filename        : draft-ietf-dnsop-rfc5011-security-considerations-03.txt
	Pages           : 13
	Date            : 2017-09-12

Abstract:
   This document extends the RFC5011 rollover strategy with timing
   advice that must be followed in order to maintain security.
   Specifically, this document describes the math behind the minimum
   time-length that a DNS zone publisher must wait before signing
   exclusively with recently added DNSKEYs.  This document also
   describes the minimum time-length that a DNS zone publisher must wait
   after publishing a revoked DNSKEY before assuming that all active
   RFC5011 resolvers should have seen the revocation-marked key and
   removed it from their list of trust anchors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc5011-security-considerations/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnsop-rfc5011-security-considerations-03
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc5011-security-considerations-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-rfc5011-security-considerations-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Sep 12 16:41:26 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD5F1343AE for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 16:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 efBFTo5IZjYf for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 16:41:24 -0700 (PDT)
Received: from mail.hardakers.net (unknown [168.150.236.43]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6E891343AD for <dnsop@ietf.org>; Tue, 12 Sep 2017 16:41:23 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 68C38243F8; Tue, 12 Sep 2017 16:41:23 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Matthijs Mekking <matthijs@pletterpet.nl>
Cc: dnsop@ietf.org
References: <ybl4luqq05v.fsf@w7.hardakers.net> <7d425067-84ff-2471-d39a-0c3a20c0116c@pletterpet.nl> <yblvakvn76v.fsf@w7.hardakers.net> <b799e983-43d8-b6db-7a13-40c5cdf37800@pletterpet.nl>
Date: Tue, 12 Sep 2017 16:41:23 -0700
In-Reply-To: <b799e983-43d8-b6db-7a13-40c5cdf37800@pletterpet.nl> (Matthijs Mekking's message of "Mon, 11 Sep 2017 13:59:40 +0200")
Message-ID: <yblwp53qycc.fsf@w7.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JOJGv2rjzT3QrVyyHe4UHl0VgYM>
Subject: Re: [DNSOP] requesting WGLC for 5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 23:41:25 -0000

Matthijs Mekking <matthijs@pletterpet.nl> writes:

>> Mathematically, I think the actually time needed to wait is 30 %
>> queryInterval, which may actually be 0 in some cases and just shy of
>> queryInterval in others.  Sound about right?
>
> I am sorry, I don't understand this logic, can you elaborate?
>
> The way I see it, queryInterval is always at minimal 1 hr and at most 15
> days (not taking into account retryTime).

In the end, the first (newly valid) time the validator queries for and
gets the new dnskey will be N minutes after the signature expiration
time.  The validators timer will start at that point.  Because
queryInterval is always equal to or less than 15 days, the validator
will always see the key twice before the 30 day window is up.  So if 30
days is a multiple of the query Interval (eg, 15 days, or 5 days) then
the first time the validator will see the key after the 30 day window is
N minutes after the expiration time plus 30 days.  Thus only 1 query
interval needs to be added in this ideal case.

The less than ideal case is when 30 isn't evenly divisible by the
queryInterval (eg, 7 days).  At which point the first time the validator
will see the new key after the (sig_exp + N + 30 days) mark will be at
(sig_exp + N + 30 days + remainder(30 days / 7)).  So we don't need to
add in a full queryInterval to cover the offset and can calculate it
instead.

(that being said, I put "you might pick 2x for simplicity" into the draft)
-- 
Wes Hardaker
USC/ISI


From nobody Tue Sep 12 17:04:17 2017
Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED17133197 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 17:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 i-TIpK1hzGbE for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 17:04:14 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68E7F13318A for <dnsop@ietf.org>; Tue, 12 Sep 2017 17:04:14 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id o42so25576550wrb.3 for <dnsop@ietf.org>; Tue, 12 Sep 2017 17:04:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hYgh0uWJlM/jbJOFAtjKH1r1DOtx/SiAJA5lGUh6bcE=; b=UNrv6wlizlHSsdcHKJKGJ0OnlSn+hgVmtRMxEIqbrwehb8xgHnuhaMfdzdL+BYTs8z TMw/v0XxMLHNiZ7gkkrVO0Z5t1TZfwuEv+pXX/SrLSSqUFQCzfLcAavL0e76ZfyOjrHZ cS1vnm7VDfwew3eC9GLArsYvG/rJCzjBPmeEEc3FM2k7sZaJlaEYoBrH7ETZgsHaGoar O/GDBKRRZSL7HWqFyz/oPhjUCQf/2gwpcZNcZwMsE1RrmGq1Dx6nzEJmFbKNe9nF3iBc awowz7tSVLA1et4jklqIKoTsI7gV3iDAtnbRLLUBLOGzbZqAIVaHRkv6NkGwVrWQ1mVM tzSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hYgh0uWJlM/jbJOFAtjKH1r1DOtx/SiAJA5lGUh6bcE=; b=LWxKJakMWmvfG+wdKFkyc8vll76wT/AwZVmh0Wsc2iGIAhX8tlqivb81LV5u0u6YnP DnVfxIdZSeoF5dS8fyuJc0CJmLrOk7pTlx27ZJI1ht5GaVy9DxYQvNsYf65HDKitLIez A++8s+4pvxeDgkGLqmCUE2TvTRoWHg3p9n8HgMmQkdF1Wm7TsUxeq5gMJgzFZtTMGFVh 6jZBZA/zkGnyRX+m+KYD4qQEaLlpayG+IrsAHU8Sfw0UXfbegq5ubhw8eF0OyTfXaR+0 89BO2+2zrARn73/a9UdtOxcs3b5D/W+4lBXaDWRHohLwIaogOzWcS6LNA3aowuEkAm3O GWMQ==
X-Gm-Message-State: AHPjjUgg9Zx7YhlEi0zm9t4+XcyJ3MkBN17bR8e5TOSdF/aIxCnMTx5P 1bMDb0aRLhW/SHoQwQ/+ooq/ZNNPaaMLBIrLYtHLNS8V
X-Google-Smtp-Source: ADKCNb4yOXtDdQhctkyWg+fOcoyAv4KEtzrgIaf08LhzRDi8o6lpCPyqT/q03jpDLQ1M7u/5WlBEMukfR9RAMnkK8jk=
X-Received: by 10.223.156.199 with SMTP id h7mr10817342wre.170.1505261052569;  Tue, 12 Sep 2017 17:04:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.141 with HTTP; Tue, 12 Sep 2017 17:03:31 -0700 (PDT)
In-Reply-To: <20170904204549.A05018415E35@rock.dv.isc.org>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <20170904204549.A05018415E35@rock.dv.isc.org>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 12 Sep 2017 20:03:31 -0400
Message-ID: <CAHw9_iLuAqRO=bQMyGeHmaeJZPdf2Q1BVaH3pg8NftJzpMSSSg@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: "Walter H." <walter.h@mathemainzel.info>, dnsop WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pdRxfnGtGEJnJlbhaQgRUjnqyXA>
Subject: Re: [DNSOP] DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 00:04:17 -0000

On Mon, Sep 4, 2017 at 4:45 PM, Mark Andrews <marka@isc.org> wrote:
>
> In message <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>, "Walter
>  H." writes:
>> On Mon, September 4, 2017 14:22, Mark Andrews wrote:
>> >
>> > In message <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail>,
>> > "Walter H." writes:
>> >> where there anyone who said: "don't use it", 15 years ago?
>> >
>> > Yes.  There were lots that discourage the use of .local, lan,
>> > .corp etc.  Just becaue you didn't hear from them doesn't mean
>> > they weren't out there.
>>
>> a discourage is not a "don't use" :-)
>
> We gave them fair warning that and domain they choose could be
> allocated in the future.  We told them to the advice you have been
> getting today.  Use a zone registered to them.  They, like you are
> today, are ignoring the advice.
>

Yup, but people continue to ignore the advice, and, as far as I can
see, will continue to do so - .internal is intended to give people a
place where they can go do whatever they want without just squatting
on something.
I personally believe they should just use something which they have
registered -- but, I also believe that abstinence is the only way to
prevent teen pregnancy. Seeing as my believing this doesn't actually
*stop* teenagers having sex, I'd like them to do so in the least risky
way possible -- .internal, a condom for the namespace.

>> >> > 'home.arpa' is in the process of being registered so that it
>> >> > can be used safely in the environment it is designed to be used in.
>> >>
>> >> yes, but commonly for residental networks, not company/enterprise
>> >> networks,
>> >> they want/need something shorter like ".corp", ".lan", ".local", ...
>> >

Perhaps corp.arpa, or internal.arpa, or home.arpa is the right answer
- unfortunately I think that they fail the "looks pretty" property.

>> > Want maybe, need absolutely not.
>> question: why isn't this the answer of a car dealer?
>
> Because the car dealer is trying to take as much money off you as
> they can.  We on the other hand are trying to save you money by
> stopping you and everyone else getting into situations that will
> cost you/them thousands of dollars to rectify in the future.
>
>> > Everyone was told to register the domain you want to use, there was
>> > no exception for active directory.

Sorry, nope. You might have said that, I might have said that, but
many people remained unaware -- also Microsoft suggested (
https://support.microsoft.com/en-us/help/296250/the-domain-name-system-name-recommendations-for-small-business-server
)

"Three practical methods to name the DNS domain are:

* Make the name a private domain name that is used for name resolution
on the internal Small Business Server network. This name is usually
configured with the first-level domain of .local. At the present time,
the .local domain name is not registered on the Internet.
* Make the name a sub-domain of a publicly registered domain name. For
example, if the publicly registered domain name is Contoso.com, a
sub-domain of Corp.contoso.com can be used.
* Make the name the same as a publicly registered domain name.

Most Small Business Server customers should use the first method. The
following list describes some of the advantages when you use a
separate and private domain name for the local Small Business Server
network:

The management of the local namespace is controlled by the Small
Business Server Server. When you use a private FQDN for local DNS name
resolution, the DNS server becomes the start of authority for the
local domain. This result means that a query to external DNS root
servers is not required for local resource name resolution.

The security may be increased for your DNS server by not enabling zone
transfers by means of the zone transfer properties of the forward
lookup zone. Because dynamic registration of internal hosts can occur
with the DNS server, if you disable the zone transfers from external
clients, you can limit the exposure of internal host names to the
Internet.

The natural separation of internal and external networks occurs
because of the use of a separate internal namespace. A client query
generated from the Internet for www.contoso.local does not return any
valid domain information because .local, at the present time, is not a
registered domain name. However, by using the Web Publishing rules in
Internet Security and Acceleration (ISA) Server, internal Web sites
can be hosted externally and viewed by using resolvable domain names.
This hosting still requires a registered domain name as well as the
appropriate public DNS records that resolve to the external IP address
of Small Business Server. Refer to "Configuring Publishing" in ISA
Server Help for more information about Web Publishing rules."


Microsoft now recommends that people put stuff under a registered
name, but a significant number of people heard (and followed) the
earlier advice.
Microsoft also used .corp (or contoso.corp) in a large number of
examples (e.g: https://blogs.technet.microsoft.com/networking/2009/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp/:
, including (IIRC) the step by step walkthrough of how to setup Active
Directory - and many people followed this --
http://www.enyo.de/fw/notes/the-great-corp-renaming.html

So, yes, people shouldn't have just used .local, or .corp -- but I
entirely understand why they did.

Reserving a TLD for internal shenanigans certainly won't fix existing
deployments. It also won't stop people from sometimes squatting on
whatever-they-feel-like. However, it will give people who are going to
do this sort of thing a safe place to do it. As Andrew says, there are
an almost unlimited number of strings that can be made with 63 octets.
I think the benefit of giving people a sandbox for this outweighs the
costs (basically none). Yes, there will be collisions if e.g.
companies merge, VPNs, and other cases (just like there were with
RFC1918); I think we need to note that as a disclaimer in the
document. People choosing to use this should be consenting adults.

>>
>> not really, at those days only a few TLDs where possible, the many TLDs
>> came some years later ...
>
> People were wanting to deploy more TLDs from the moment the Internet
> was opened up to the public.
>
>> by the way: where is the problem with .home or .corp?
>> I ask this, because at my hoster I pre-reserved my "local domain" - a
>> .home, that I have used for many years several zears ago and nothing
>> happened ...
>>
>> > IPv6 would have been deployed a lot sooner. :-)
>>
>> not really, my ISP is still IPv4 only ..., my IPv6 connectivity is a
>> HE-tunnel ...
>> and the brand new OS from Microsoft still has the bugs inside: TEREDO, ...
>> which I had to deactivate first, before it is usable with IPv6 at all ...
>
> If you didn't have the relief valve of RFC 1918 addresses then yes
> IPv6 would have come a lot quicker and stuff like TEREDO wouldn't
> exist.
>
>> > Except such systems exist.  Go look at what a Mac does.  ping for
>> > test.local and look and port 5353 traffic and compare it to port 53
>> > traffic.
>>
>> I know, this RFC was written by Apple;
>>
>> no Apple no problem, I would say :-)
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Tue Sep 12 18:54:42 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EAD7133209 for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 18:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UyCyM6xVGo7A for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 18:54:38 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCCB7132F2E for <dnsop@ietf.org>; Tue, 12 Sep 2017 18:54:37 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id n69so55727182ioi.5 for <dnsop@ietf.org>; Tue, 12 Sep 2017 18:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=YprYatw2tHuKi+wSxASreVr1XLGFCovs77BgBBi+EQY=; b=eDa7imNpaM4cG1nwpp/qOrdgON+nV/PyZ95YS5gKCOswC47JcF7YL+FhzxUOFUhaB+ 56mo/CeQAmKZ5x9Wa4YMvGHUqrWAvninLaXtzKcGJY0knoGTVR9BzzW3AekJ22m3p4ci 7qQ2LMQzuUlojPS+KxLlmkxsJ0oZ7F1RJKAudzOh/2w+qUiyqi+Dfnabs4v9e9xedr3G dBWAumkKP+Sq8ffXyxIdYVpE3Ch3hpHPRKlxwkITPI/0ft3E4TSQPuiEjYv21p1gNrpQ X9Wnh0fBO9qSEOSg+uqfBqcL5SeMxfw5QhPF7PanZmAzGC/C9iOkj9eBqdlpXbz/uWzo 941Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=YprYatw2tHuKi+wSxASreVr1XLGFCovs77BgBBi+EQY=; b=UKxYzaGldNENEDpL4VQHSa9vP3UAjk5sWnGpYabNH9u/PE+kRtHsjUa3HPM0sy5GPm ztSEI1hnQ3nTfI3F88YxUXvI4GKA3nE6tSdz/ZXYHmY4gCGWR6GTGdqCQEw9xQHSPaop MY35FDmBssj0wB+GhTcH15aJ/ipyeFmx9EtOy3GRbChYuEn/uFy4CLRIMOTS0JTbQTkc jT0WX0+l9F4XrmXcwrh3WHVT1A5qrlgE9jSQbI3nXtoQZQhrBO4qIqth9njddok/MMv9 B5+r8LtVEpsXaTifltjH1fhaxZHp1714Ey8pHzE7mJvN1EHiEByfc6SnAup6zdfVGVm0 JJUA==
X-Gm-Message-State: AHPjjUgC3y2RioH/4ya8iJYFrssjy6ExHPsddJYHA3r2C+J0bSZ+JOn+ eKiuZr+yxxQfLE8DkUKm5Lrw1VVV5ZZ5GVd6nvQ=
X-Google-Smtp-Source: AOwi7QAQVlFCBYmihjQGY/tkw/3hv240HttQXctAU6Fep1INV1rWhbs5P3R7opTR4Ovc4jLX/IEmDabn8ZeB36JCQ8w=
X-Received: by 10.107.130.224 with SMTP id m93mr27547367ioi.82.1505267676732;  Tue, 12 Sep 2017 18:54:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.22.67 with HTTP; Tue, 12 Sep 2017 18:54:36 -0700 (PDT)
In-Reply-To: <CACfw2hjMLXYqXg+6ea1G0aPntX2UnM_ufMZFqNmn4GKVDvcu8w@mail.gmail.com>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.DEB.2.11.1709012044210.2676@grey.csi.cam.ac.uk> <59A9BCA2.6060008@mathemainzel.info> <20170903043202.GA18082@besserwisser.org> <59AC4E42.9080600@mathemainzel.info> <60304450-DFA3-4982-B01D-CC33C49BDCFC@isc.org> <59f8c88caaf82a5884aa87223d49e7e4.1504505559@squirrel.mail> <3B75D240-13B9-4A94-B56D-24E83B4A4A8F@rfc1035.com> <3fe7bc511a990b0288b645dc176e1ef3.1504515284@squirrel.mail> <20170904090455.4249F8411CFC@rock.dv.isc.org> <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail> <20170904122222.C270F8413534@rock.dv.isc.org> <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail> <20170904204549.A05018415E35@rock.dv.isc.org> <CAHw9_iLuAqRO=bQMyGeHmaeJZPdf2Q1BVaH3pg8NftJzpMSSSg@mail.gmail.com> <CACfw2hjMLXYqXg+6ea1G0aPntX2UnM_ufMZFqNmn4GKVDvcu8w@mail.gmail.com>
From: william manning <chinese.apricot@gmail.com>
Date: Tue, 12 Sep 2017 18:54:36 -0700
Message-ID: <CACfw2hi-nVDi0yai7H0G2zkFJwXbkZALdpQuXpHc60QyiiQtzA@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eee7c29e55f055908711b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iWYoMeuikFcSG_h-m_AMjReooEI>
Subject: [DNSOP] Fwd:  DNSSEC in local networks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 01:54:41 -0000

--001a113eee7c29e55f055908711b
Content-Type: text/plain; charset="UTF-8"

'cause warren isn't special enough to warrant getting the only copy of this.

/Wm
---------- Forwarded message ----------
From: william manning <chinese.apricot@gmail.com>
Date: Tue, Sep 12, 2017 at 6:53 PM
Subject: Re: [DNSOP] DNSSEC in local networks
To: Warren Kumari <warren@kumari.net>


cry me a river.  in the face of conflicting strings, tie-break by using the
closest enclosing trust anchor. See the "Islands of Trust" RFCs.  Slavish
dependence on a single trust anchor is among the dumber things you can do,
operationally.

/Wm

On Tue, Sep 12, 2017 at 5:03 PM, Warren Kumari <warren@kumari.net> wrote:

> On Mon, Sep 4, 2017 at 4:45 PM, Mark Andrews <marka@isc.org> wrote:
> >
> > In message <efe320cf9580d4c1bb2b26dd1c294306.1504529679@squirrel.mail>,
> "Walter
> >  H." writes:
> >> On Mon, September 4, 2017 14:22, Mark Andrews wrote:
> >> >
> >> > In message <c0c73dab49c6452c616c86656704ecd0.1504518603@squirrel.mail
> >,
> >> > "Walter H." writes:
> >> >> where there anyone who said: "don't use it", 15 years ago?
> >> >
> >> > Yes.  There were lots that discourage the use of .local, lan,
> >> > .corp etc.  Just becaue you didn't hear from them doesn't mean
> >> > they weren't out there.
> >>
> >> a discourage is not a "don't use" :-)
> >
> > We gave them fair warning that and domain they choose could be
> > allocated in the future.  We told them to the advice you have been
> > getting today.  Use a zone registered to them.  They, like you are
> > today, are ignoring the advice.
> >
>
> Yup, but people continue to ignore the advice, and, as far as I can
> see, will continue to do so - .internal is intended to give people a
> place where they can go do whatever they want without just squatting
> on something.
> I personally believe they should just use something which they have
> registered -- but, I also believe that abstinence is the only way to
> prevent teen pregnancy. Seeing as my believing this doesn't actually
> *stop* teenagers having sex, I'd like them to do so in the least risky
> way possible -- .internal, a condom for the namespace.
>
> >> >> > 'home.arpa' is in the process of being registered so that it
> >> >> > can be used safely in the environment it is designed to be used in.
> >> >>
> >> >> yes, but commonly for residental networks, not company/enterprise
> >> >> networks,
> >> >> they want/need something shorter like ".corp", ".lan", ".local", ...
> >> >
>
> Perhaps corp.arpa, or internal.arpa, or home.arpa is the right answer
> - unfortunately I think that they fail the "looks pretty" property.
>
> >> > Want maybe, need absolutely not.
> >> question: why isn't this the answer of a car dealer?
> >
> > Because the car dealer is trying to take as much money off you as
> > they can.  We on the other hand are trying to save you money by
> > stopping you and everyone else getting into situations that will
> > cost you/them thousands of dollars to rectify in the future.
> >
> >> > Everyone was told to register the domain you want to use, there was
> >> > no exception for active directory.
>
> Sorry, nope. You might have said that, I might have said that, but
> many people remained unaware -- also Microsoft suggested (
> https://support.microsoft.com/en-us/help/296250/the-domain-n
> ame-system-name-recommendations-for-small-business-server
> )
>
> "Three practical methods to name the DNS domain are:
>
> * Make the name a private domain name that is used for name resolution
> on the internal Small Business Server network. This name is usually
> configured with the first-level domain of .local. At the present time,
> the .local domain name is not registered on the Internet.
> * Make the name a sub-domain of a publicly registered domain name. For
> example, if the publicly registered domain name is Contoso.com, a
> sub-domain of Corp.contoso.com can be used.
> * Make the name the same as a publicly registered domain name.
>
> Most Small Business Server customers should use the first method. The
> following list describes some of the advantages when you use a
> separate and private domain name for the local Small Business Server
> network:
>
> The management of the local namespace is controlled by the Small
> Business Server Server. When you use a private FQDN for local DNS name
> resolution, the DNS server becomes the start of authority for the
> local domain. This result means that a query to external DNS root
> servers is not required for local resource name resolution.
>
> The security may be increased for your DNS server by not enabling zone
> transfers by means of the zone transfer properties of the forward
> lookup zone. Because dynamic registration of internal hosts can occur
> with the DNS server, if you disable the zone transfers from external
> clients, you can limit the exposure of internal host names to the
> Internet.
>
> The natural separation of internal and external networks occurs
> because of the use of a separate internal namespace. A client query
> generated from the Internet for www.contoso.local does not return any
> valid domain information because .local, at the present time, is not a
> registered domain name. However, by using the Web Publishing rules in
> Internet Security and Acceleration (ISA) Server, internal Web sites
> can be hosted externally and viewed by using resolvable domain names.
> This hosting still requires a registered domain name as well as the
> appropriate public DNS records that resolve to the external IP address
> of Small Business Server. Refer to "Configuring Publishing" in ISA
> Server Help for more information about Web Publishing rules."
>
>
> Microsoft now recommends that people put stuff under a registered
> name, but a significant number of people heard (and followed) the
> earlier advice.
> Microsoft also used .corp (or contoso.corp) in a large number of
> examples (e.g: https://blogs.technet.microsoft.com/networking/2009/04/16/
> dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp/:
> , including (IIRC) the step by step walkthrough of how to setup Active
> Directory - and many people followed this --
> http://www.enyo.de/fw/notes/the-great-corp-renaming.html
>
> So, yes, people shouldn't have just used .local, or .corp -- but I
> entirely understand why they did.
>
> Reserving a TLD for internal shenanigans certainly won't fix existing
> deployments. It also won't stop people from sometimes squatting on
> whatever-they-feel-like. However, it will give people who are going to
> do this sort of thing a safe place to do it. As Andrew says, there are
> an almost unlimited number of strings that can be made with 63 octets.
> I think the benefit of giving people a sandbox for this outweighs the
> costs (basically none). Yes, there will be collisions if e.g.
> companies merge, VPNs, and other cases (just like there were with
> RFC1918); I think we need to note that as a disclaimer in the
> document. People choosing to use this should be consenting adults.
>
> >>
> >> not really, at those days only a few TLDs where possible, the many TLDs
> >> came some years later ...
> >
> > People were wanting to deploy more TLDs from the moment the Internet
> > was opened up to the public.
> >
> >> by the way: where is the problem with .home or .corp?
> >> I ask this, because at my hoster I pre-reserved my "local domain" - a
> >> .home, that I have used for many years several zears ago and nothing
> >> happened ...
> >>
> >> > IPv6 would have been deployed a lot sooner. :-)
> >>
> >> not really, my ISP is still IPv4 only ..., my IPv6 connectivity is a
> >> HE-tunnel ...
> >> and the brand new OS from Microsoft still has the bugs inside: TEREDO,
> ...
> >> which I had to deactivate first, before it is usable with IPv6 at all
> ...
> >
> > If you didn't have the relief valve of RFC 1918 addresses then yes
> > IPv6 would have come a lot quicker and stuff like TEREDO wouldn't
> > exist.
> >
> >> > Except such systems exist.  Go look at what a Mac does.  ping for
> >> > test.local and look and port 5353 traffic and compare it to port 53
> >> > traffic.
> >>
> >> I know, this RFC was written by Apple;
> >>
> >> no Apple no problem, I would say :-)
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742 <+61%202%209871%204742>
>  INTERNET: marka@isc.org
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--001a113eee7c29e55f055908711b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&#39;cause warren isn&#39;t special enough to warrant gett=
ing the only copy of this.<div><br></div><div>/Wm<br><div class=3D"gmail_qu=
ote">---------- Forwarded message ----------<br>From: <b class=3D"gmail_sen=
dername">william manning</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:chines=
e.apricot@gmail.com">chinese.apricot@gmail.com</a>&gt;</span><br>Date: Tue,=
 Sep 12, 2017 at 6:53 PM<br>Subject: Re: [DNSOP] DNSSEC in local networks<b=
r>To: Warren Kumari &lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.=
net</a>&gt;<br><br><br><div dir=3D"ltr">cry me a river. =C2=A0in the face o=
f conflicting strings, tie-break by using the closest enclosing trust ancho=
r. See the &quot;Islands of Trust&quot; RFCs.=C2=A0 Slavish dependence on a=
 single trust anchor is among the dumber things you can do, operationally.<=
span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>/Wm</div>=
</font></span></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Tue, Sep 12, 2017 at 5:03 PM,=
 Warren Kumari <span dir=3D"ltr">&lt;<a href=3D"mailto:warren@kumari.net" t=
arget=3D"_blank">warren@kumari.net</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><span>On Mon, Sep 4, 2017 at 4:45 PM, Mark Andrews &lt;<a h=
ref=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt; wrote:=
<br>
&gt;<br>
&gt; In message &lt;efe320cf9580d4c1bb2b26dd1c294<wbr>306.1504529679@squirr=
el.mail&gt;, &quot;Walter<br>
&gt;=C2=A0 H.&quot; writes:<br>
&gt;&gt; On Mon, September 4, 2017 14:22, Mark Andrews wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; In message &lt;c0c73dab49c6452c616c86656704e<wbr>cd0.15045186=
03@squirrel.mail&gt;,<br>
&gt;&gt; &gt; &quot;Walter H.&quot; writes:<br>
&gt;&gt; &gt;&gt; where there anyone who said: &quot;don&#39;t use it&quot;=
, 15 years ago?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Yes.=C2=A0 There were lots that discourage the use of .local,=
 lan,<br>
&gt;&gt; &gt; .corp etc.=C2=A0 Just becaue you didn&#39;t hear from them do=
esn&#39;t mean<br>
&gt;&gt; &gt; they weren&#39;t out there.<br>
&gt;&gt;<br>
&gt;&gt; a discourage is not a &quot;don&#39;t use&quot; :-)<br>
&gt;<br>
&gt; We gave them fair warning that and domain they choose could be<br>
&gt; allocated in the future.=C2=A0 We told them to the advice you have bee=
n<br>
&gt; getting today.=C2=A0 Use a zone registered to them.=C2=A0 They, like y=
ou are<br>
&gt; today, are ignoring the advice.<br>
&gt;<br>
<br>
</span>Yup, but people continue to ignore the advice, and, as far as I can<=
br>
see, will continue to do so - .internal is intended to give people a<br>
place where they can go do whatever they want without just squatting<br>
on something.<br>
I personally believe they should just use something which they have<br>
registered -- but, I also believe that abstinence is the only way to<br>
prevent teen pregnancy. Seeing as my believing this doesn&#39;t actually<br=
>
*stop* teenagers having sex, I&#39;d like them to do so in the least risky<=
br>
way possible -- .internal, a condom for the namespace.<br>
<span><br>
&gt;&gt; &gt;&gt; &gt; &#39;home.arpa&#39; is in the process of being regis=
tered so that it<br>
&gt;&gt; &gt;&gt; &gt; can be used safely in the environment it is designed=
 to be used in.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; yes, but commonly for residental networks, not company/en=
terprise<br>
&gt;&gt; &gt;&gt; networks,<br>
&gt;&gt; &gt;&gt; they want/need something shorter like &quot;.corp&quot;, =
&quot;.lan&quot;, &quot;.local&quot;, ...<br>
&gt;&gt; &gt;<br>
<br>
</span>Perhaps corp.arpa, or internal.arpa, or home.arpa is the right answe=
r<br>
- unfortunately I think that they fail the &quot;looks pretty&quot; propert=
y.<br>
<span><br>
&gt;&gt; &gt; Want maybe, need absolutely not.<br>
&gt;&gt; question: why isn&#39;t this the answer of a car dealer?<br>
&gt;<br>
&gt; Because the car dealer is trying to take as much money off you as<br>
&gt; they can.=C2=A0 We on the other hand are trying to save you money by<b=
r>
&gt; stopping you and everyone else getting into situations that will<br>
&gt; cost you/them thousands of dollars to rectify in the future.<br>
&gt;<br>
&gt;&gt; &gt; Everyone was told to register the domain you want to use, the=
re was<br>
&gt;&gt; &gt; no exception for active directory.<br>
<br>
</span>Sorry, nope. You might have said that, I might have said that, but<b=
r>
many people remained unaware -- also Microsoft suggested (<br>
<a href=3D"https://support.microsoft.com/en-us/help/296250/the-domain-name-=
system-name-recommendations-for-small-business-server" rel=3D"noreferrer" t=
arget=3D"_blank">https://support.microsoft.com/<wbr>en-us/help/296250/the-d=
omain-n<wbr>ame-system-name-recommendation<wbr>s-for-small-business-server<=
/a><br>
)<br>
<br>
&quot;Three practical methods to name the DNS domain are:<br>
<br>
* Make the name a private domain name that is used for name resolution<br>
on the internal Small Business Server network. This name is usually<br>
configured with the first-level domain of .local. At the present time,<br>
the .local domain name is not registered on the Internet.<br>
* Make the name a sub-domain of a publicly registered domain name. For<br>
example, if the publicly registered domain name is Contoso.com, a<br>
sub-domain of <a href=3D"http://Corp.contoso.com" rel=3D"noreferrer" target=
=3D"_blank">Corp.contoso.com</a> can be used.<br>
* Make the name the same as a publicly registered domain name.<br>
<br>
Most Small Business Server customers should use the first method. The<br>
following list describes some of the advantages when you use a<br>
separate and private domain name for the local Small Business Server<br>
network:<br>
<br>
The management of the local namespace is controlled by the Small<br>
Business Server Server. When you use a private FQDN for local DNS name<br>
resolution, the DNS server becomes the start of authority for the<br>
local domain. This result means that a query to external DNS root<br>
servers is not required for local resource name resolution.<br>
<br>
The security may be increased for your DNS server by not enabling zone<br>
transfers by means of the zone transfer properties of the forward<br>
lookup zone. Because dynamic registration of internal hosts can occur<br>
with the DNS server, if you disable the zone transfers from external<br>
clients, you can limit the exposure of internal host names to the<br>
Internet.<br>
<br>
The natural separation of internal and external networks occurs<br>
because of the use of a separate internal namespace. A client query<br>
generated from the Internet for www.contoso.local does not return any<br>
valid domain information because .local, at the present time, is not a<br>
registered domain name. However, by using the Web Publishing rules in<br>
Internet Security and Acceleration (ISA) Server, internal Web sites<br>
can be hosted externally and viewed by using resolvable domain names.<br>
This hosting still requires a registered domain name as well as the<br>
appropriate public DNS records that resolve to the external IP address<br>
of Small Business Server. Refer to &quot;Configuring Publishing&quot; in IS=
A<br>
Server Help for more information about Web Publishing rules.&quot;<br>
<br>
<br>
Microsoft now recommends that people put stuff under a registered<br>
name, but a significant number of people heard (and followed) the<br>
earlier advice.<br>
Microsoft also used .corp (or contoso.corp) in a large number of<br>
examples (e.g: <a href=3D"https://blogs.technet.microsoft.com/networking/20=
09/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp=
/" rel=3D"noreferrer" target=3D"_blank">https://blogs.technet.microsof<wbr>=
t.com/networking/2009/04/16/<wbr>dns-client-name-resolution-<wbr>behavior-i=
n-windows-vista-vs-<wbr>windows-xp/</a>:<br>
, including (IIRC) the step by step walkthrough of how to setup Active<br>
Directory - and many people followed this --<br>
<a href=3D"http://www.enyo.de/fw/notes/the-great-corp-renaming.html" rel=3D=
"noreferrer" target=3D"_blank">http://www.enyo.de/fw/notes/th<wbr>e-great-c=
orp-renaming.html</a><br>
<br>
So, yes, people shouldn&#39;t have just used .local, or .corp -- but I<br>
entirely understand why they did.<br>
<br>
Reserving a TLD for internal shenanigans certainly won&#39;t fix existing<b=
r>
deployments. It also won&#39;t stop people from sometimes squatting on<br>
whatever-they-feel-like. However, it will give people who are going to<br>
do this sort of thing a safe place to do it. As Andrew says, there are<br>
an almost unlimited number of strings that can be made with 63 octets.<br>
I think the benefit of giving people a sandbox for this outweighs the<br>
costs (basically none). Yes, there will be collisions if e.g.<br>
companies merge, VPNs, and other cases (just like there were with<br>
RFC1918); I think we need to note that as a disclaimer in the<br>
document. People choosing to use this should be consenting adults.<br>
<div class=3D"m_4516000033282121926HOEnZb"><div class=3D"m_4516000033282121=
926h5"><br>
&gt;&gt;<br>
&gt;&gt; not really, at those days only a few TLDs where possible, the many=
 TLDs<br>
&gt;&gt; came some years later ...<br>
&gt;<br>
&gt; People were wanting to deploy more TLDs from the moment the Internet<b=
r>
&gt; was opened up to the public.<br>
&gt;<br>
&gt;&gt; by the way: where is the problem with .home or .corp?<br>
&gt;&gt; I ask this, because at my hoster I pre-reserved my &quot;local dom=
ain&quot; - a<br>
&gt;&gt; .home, that I have used for many years several zears ago and nothi=
ng<br>
&gt;&gt; happened ...<br>
&gt;&gt;<br>
&gt;&gt; &gt; IPv6 would have been deployed a lot sooner. :-)<br>
&gt;&gt;<br>
&gt;&gt; not really, my ISP is still IPv4 only ..., my IPv6 connectivity is=
 a<br>
&gt;&gt; HE-tunnel ...<br>
&gt;&gt; and the brand new OS from Microsoft still has the bugs inside: TER=
EDO, ...<br>
&gt;&gt; which I had to deactivate first, before it is usable with IPv6 at =
all ...<br>
&gt;<br>
&gt; If you didn&#39;t have the relief valve of RFC 1918 addresses then yes=
<br>
&gt; IPv6 would have come a lot quicker and stuff like TEREDO wouldn&#39;t<=
br>
&gt; exist.<br>
&gt;<br>
&gt;&gt; &gt; Except such systems exist.=C2=A0 Go look at what a Mac does.=
=C2=A0 ping for<br>
&gt;&gt; &gt; test.local and look and port 5353 traffic and compare it to p=
ort 53<br>
&gt;&gt; &gt; traffic.<br>
&gt;&gt;<br>
&gt;&gt; I know, this RFC was written by Apple;<br>
&gt;&gt;<br>
&gt;&gt; no Apple no problem, I would say :-)<br>
&gt; --<br>
&gt; Mark Andrews, ISC<br>
&gt; 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
&gt; PHONE: <a href=3D"tel:+61%202%209871%204742" value=3D"+61298714742" ta=
rget=3D"_blank">+61 2 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0INTERNET: <a href=3D"mailto:marka@isc.org" target=
=3D"_blank">marka@isc.org</a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; DNSOP mailing list<br>
&gt; <a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/dnsop</a>=
<br>
<br>
<br>
<br>
</div></div><span class=3D"m_4516000033282121926HOEnZb"><font color=3D"#888=
888">--<br>
I don&#39;t think the execution is relevant when it was obviously a bad<br>
idea in the first place.<br>
This is like putting rabid weasels in your pants, and later expressing<br>
regret at having chosen those particular rabid weasels and that pair<br>
of pants.<br>
=C2=A0 =C2=A0---maf<br>
</font></span><div class=3D"m_4516000033282121926HOEnZb"><div class=3D"m_45=
16000033282121926h5"><br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>
</div></div></div><br></div></div>

--001a113eee7c29e55f055908711b--


From nobody Tue Sep 12 19:15:56 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 092FD13292A for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 19:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 jcO7Uu2MPUcc for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 19:15:53 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBE61126C19 for <dnsop@ietf.org>; Tue, 12 Sep 2017 19:15:52 -0700 (PDT)
Received: (qmail 27447 invoked by uid 125); 13 Sep 2017 02:15:51 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 13 Sep 2017 02:15:51 -0000
Date: 13 Sep 2017 02:15:29 -0000
Message-ID: <20170913021529.2540.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: peter.van.dijk@powerdns.com
In-Reply-To: <63DA2E77-8507-4F25-8684-14EABF9A530E@powerdns.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RWjExwIIn07u-PPl8DqgYyZDyoU>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 02:15:55 -0000

In article <63DA2E77-8507-4F25-8684-14EABF9A530E@powerdns.com> you write:
>Since we are doing a draft/RFC on what localhost is and is not, I 
>suggest we put some text in there banning (MUST NOT) the practice of 
>having localhost entries (at least those pointing to 127.0.0.1/::1?) in 
>auth zones. If there is agreement on this I am happy to contribute text. 
>This may mean having to say we are updating RFC 1912.

Believe it or not, there are real non-loopback localhost domain names,
like localhost.reddit.com.

I agree that localhost.<foo> pointing to loopback is generally asking
for trouble, but I am not at this point sufficiently confident that it
is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
can for example imagine ways that might make some kinds of debugging
easier.

R's,
John


From nobody Tue Sep 12 19:45:36 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEBE313352A for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 19:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 FBZ8PMyRjBuM for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 19:45:30 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBBB013343C for <dnsop@ietf.org>; Tue, 12 Sep 2017 19:45:29 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id s18so27835599qta.3 for <dnsop@ietf.org>; Tue, 12 Sep 2017 19:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=EiKwzrM5cOFyQ1GtmPNcZlCmO3nfxtbQbyiOd81ea/c=; b=kfYsbe6Ei0K+wU9jRzQl6NCP5M9FsssgFXWe9bCrX5e+2LJXrMkPguXykJSr/rXmBW y1ROPvBW+fCIvGPJNSqgX1cz39on4HQXnITNxxxC0R1yLvL5mzfK74J/x+I9jY2eAlJX miDV8RRpbhtT6ihdZS2kJJzVc8sOhgVOVm7l7njIc4naHleavSGqotMk4fDSXQRIYcto 0lyit3R9kDbjIUnBTHYgmHHglONEZ8DcCJZY6gICVaWJuyRTjICNF4DPxTn/e8R/wlue GuHzUNDHV1gwmiaE+476WxE6HRiEuUeeOCd1TJljlw2EBFx6imLClAUbGNwZxiG9JGNq N2mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=EiKwzrM5cOFyQ1GtmPNcZlCmO3nfxtbQbyiOd81ea/c=; b=BJccYajeWc5Qb/hJ6lkgcGPdLL31wCb3kwuYDl1k1VgwmVKExuTi9USxC1lGcKVqnw RKT/BCSgTd5BDqcYgGrmCcftQOcE6M6h9iyOdznTUA5xBEnJhNXj6912JrZII+KstfQJ G9k4yDEHEahympAhKc6IBE6FdAgwpTrxVknkS8TfOBUIY/GqoZrB65KVk8iOEswCRgyp y/4HT4vQPNHA//4b/1hPlRkd2HuBsegtyQPYGWra//WH7EQs+rRo/U48j7m8oeo+m2Gs FJ77Cyd8t0SCN8FsDq5TMX6Afhb2VY5NPs55fAYl72Gp1FFOjd5cuUd7WzjO76lNvDbu sE1g==
X-Gm-Message-State: AHPjjUgp9IXg380nf+Z5X9Em4LEJXlowj5IJfoiFTDTDEThvKqGqEeZm J31WGWwiAl3howo27ksVCw==
X-Google-Smtp-Source: AOwi7QCYFn8OC8/ftt8geS1ADYhKBVpxcP6BGslpPhYawiP5ulyqIXDCy5cb+jg8YkxiALHe1O/xOQ==
X-Received: by 10.237.34.56 with SMTP id n53mr13094760qtc.140.1505270728760; Tue, 12 Sep 2017 19:45:28 -0700 (PDT)
Received: from [10.0.30.153] (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id m29sm7910163qtk.58.2017.09.12.19.45.27 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Sep 2017 19:45:27 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0B99641B-8F74-432D-9E93-8452D755ADB8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 12 Sep 2017 22:45:26 -0400
References: <20170913021529.2540.qmail@ary.lan>
To: dnsop WG <dnsop@ietf.org>
In-Reply-To: <20170913021529.2540.qmail@ary.lan>
Message-Id: <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/m5V2y2pS9WnA4x2WHH3ySFI17TQ>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 02:45:36 -0000

--Apple-Mail=_0B99641B-8F74-432D-9E93-8452D755ADB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 12, 2017, at 10:15 PM, John Levine <johnl@taugh.com> wrote:
> Believe it or not, there are real non-loopback localhost domain names,
> like localhost.reddit.com <http://localhost.reddit.com/>.
>=20
> I agree that localhost.<foo> pointing to loopback is generally asking
> for trouble, but I am not at this point sufficiently confident that it
> is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
> can for example imagine ways that might make some kinds of debugging
> easier.

When we look at edge cases like this, it's tempting to be swept away by =
the futility of trying to close every gap.   But it's still worth =
closing the ones we can close.   Trying to outlaw localhost.* is =
hopeless.  But outlawing *.localhost is certainly valid and viable, and =
as DNSSEC adoption increases, more and more it will be the case that we =
actually need do nothing to break it.   "localhost" + search list still =
fails unsafe.

This is just another reason to outlaw search lists.   I can't think what =
use case search lists address that's worth the security vulnerability =
they create.   The fact that hosts routinely use search lists provided =
by DHCP is something that just astonishes me, but even user-configured =
search lists serve no useful purpose to anyone but the statistically =
negligible set of geeks who actually type in domain names and yet =
haven't become paranoid enough to realize that search lists are bad yet. =
  There is no downside to deprecating them.

(Should someone reading this be one of those network operators who still =
puts search lists to some use inside of their firewall, please do not =
tell us about it.   I do not want to be the cause of your users being =
hacked.)


--Apple-Mail=_0B99641B-8F74-432D-9E93-8452D755ADB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 12, 2017, at 10:15 PM, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Believe it or not, =
there are real non-loopback localhost domain names,</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">like<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"http://localhost.reddit.com/" style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">localhost.reddit.com</a><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">I agree that localhost.&lt;foo&gt; =
pointing to loopback is generally asking</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">for trouble, but I =
am not at this point sufficiently confident that it</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">is never ever a good idea to say MUST NOT rather =
than SHOULD NOT. &nbsp;I</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">can for example =
imagine ways that might make some kinds of debugging</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">easier.</span></div></blockquote></div><br =
class=3D""><div class=3D"">When we look at edge cases like this, it's =
tempting to be swept away by the futility of trying to close every gap. =
&nbsp; But it's still worth closing the ones we can close. &nbsp; Trying =
to outlaw localhost.* is hopeless. &nbsp;But outlawing *.localhost is =
certainly valid and viable, and as DNSSEC adoption increases, more and =
more it will be the case that we actually need do nothing to break it. =
&nbsp; "localhost" + search list still fails unsafe.</div><div =
class=3D""><br class=3D""></div><div class=3D"">This is just another =
reason to outlaw search lists. &nbsp; I can't think what use case search =
lists address that's worth the security vulnerability they create. =
&nbsp; The fact that hosts routinely use search lists provided by DHCP =
is something that just astonishes me, but even user-configured search =
lists serve no useful purpose to anyone but the statistically negligible =
set of geeks who actually type in domain names and yet haven't become =
paranoid enough to realize that search lists are bad yet. &nbsp; There =
is no downside to deprecating them.</div><div class=3D""><br =
class=3D""></div><div class=3D"">(Should someone reading this be one of =
those network operators who still puts search lists to some use inside =
of their firewall, please do not tell us about it. &nbsp; I do not want =
to be the cause of your users being hacked.)</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_0B99641B-8F74-432D-9E93-8452D755ADB8--


From nobody Tue Sep 12 20:06:52 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0715B1333FC for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 20:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 QxhaOo_nfNhx for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 20:06:50 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2D7713292E for <dnsop@ietf.org>; Tue, 12 Sep 2017 20:06:50 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 07FAA34CEB1; Wed, 13 Sep 2017 03:06:48 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id DC64A160074; Wed, 13 Sep 2017 03:06:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C2D28160069; Wed, 13 Sep 2017 03:06:47 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 98M87peU9YUv; Wed, 13 Sep 2017 03:06:47 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 71C8116005C; Wed, 13 Sep 2017 03:06:47 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 946E8855120E; Wed, 13 Sep 2017 13:06:45 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: dnsop WG <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <20170913021529.2540.qmail@ary.lan> <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com>
In-reply-to: Your message of "Tue, 12 Sep 2017 22:45:26 -0400." <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com>
Date: Wed, 13 Sep 2017 13:06:45 +1000
Message-Id: <20170913030645.946E8855120E@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZahbnzjwFND3gDVO_pD6Tpz3DIo>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 03:06:52 -0000

In message <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com>, Ted Lemon writes:
> On Sep 12, 2017, at 10:15 PM, John Levine <johnl@taugh.com> wrote:
> > Believe it or not, there are real non-loopback localhost domain names,
> > like localhost.reddit.com <http://localhost.reddit.com/>.
> >
> > I agree that localhost.<foo> pointing to loopback is generally asking
> > for trouble, but I am not at this point sufficiently confident that it
> > is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
> > can for example imagine ways that might make some kinds of debugging
> > easier.
>
> When we look at edge cases like this, it's tempting to be swept away by
> the futility of trying to close every gap.   But it's still worth closing
> the ones we can close.   Trying to outlaw localhost.* is hopeless.  But
> outlawing *.localhost is certainly valid and viable, and as DNSSEC
> adoption increases, more and more it will be the case that we actually
> need do nothing to break it.   "localhost" + search list still fails
> unsafe.

Why would we want to outlaw *.localhost?  Just because it is
inconvient for the IAB and ICANN that they didn't address this issue
correctly years ago.

Oh sorry you can't use SRV with localhost to assign a port to this
protocol THAT HAS NO DEFAULT PORT and only a NAME.  Is this what you
REALLY want to do?

> This is just another reason to outlaw search lists.   I can't think what
> use case search lists address that's worth the security vulnerability
> they create.   The fact that hosts routinely use search lists provided by
> DHCP is something that just astonishes me, but even user-configured
> search lists serve no useful purpose to anyone but the statistically
> negligible set of geeks who actually type in domain names and yet haven't
> become paranoid enough to realize that search lists are bad yet.   There
> is no downside to deprecating them.
>
> (Should someone reading this be one of those network operators who still
> puts search lists to some use inside of their firewall, please do not
> tell us about it.   I do not want to be the cause of your users being
> hacked.)

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Sep 12 20:14:12 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920C213352B for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 20:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 065P8oM2szVf for <dnsop@ietfa.amsl.com>; Tue, 12 Sep 2017 20:14:09 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10AB413292F for <dnsop@ietf.org>; Tue, 12 Sep 2017 20:14:09 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id q8so29708786qtb.5 for <dnsop@ietf.org>; Tue, 12 Sep 2017 20:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3ICK1IuvcQZwVvaKIB6rzy7kOtb3JL7dbKxk0J+UYDc=; b=1Fz1apda1PGLl/JqqQzXAZKSWyL1hCKj7r/S5OHVaIQcBJMG2jSC1YnYcJC+eQM8y/ 4UNtisixtmYvc7zzyR68z3tjXIeMLySvEho4jpIk65AyT8daKTG1r9M9RfUPwdjLD/Ep 4szZXNFKFB0OqdqYFKmWaL9uNTcez6M1k+n5PJk0n6rrIOB74sYc/Nvab5lh59anesqY N5mpXa/Sw2j+A4ZoBeEig+tF9zzXGyM9N6sk9qnYiPdBtJ3Nh6UQToXcu3sFCSKLHIFk fqhmJRotzavdEyAaZpa4dqHng1qfOuvX5Hqbjm52MnCqGfco2ryqPoD06r5/2nrZ/ayh 0ciw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3ICK1IuvcQZwVvaKIB6rzy7kOtb3JL7dbKxk0J+UYDc=; b=t3/F+6FbetP/OGu7xnR/G2dG/L8CDbWlChrhsEv9Ddja/d3XE+mwXSAamOD1N4W+PI 9EqmREIHgSydPl6HmNhAPiauSkOAQDMKg7inBqTO60KH+tVSi0IyorVZzo7UcgHO7XDZ kgjlGJc0H7a1Wi0tiTiSiHDg2QNWx9ju/6u640Hcdvnw3LzET3WbwQF3muMpmaMe6sUk 1j51W/Y4QC2Pf6LfwAXnKNifCZ/q5cyreJxdRfmpZw1XoE8WC3mEhrzaJ2AWv9XhpsuC 8RNoe1FXZD2OIcYkqIXL7GAv7WNJb9/1zcT7tTsKkAZfBfdjCToLGW8MsSwxTiZ3K3cS 8y0Q==
X-Gm-Message-State: AHPjjUjzx9Q0canLsoj+179A3iSPLflOT6f+iarDXsJofTF04QcjQfds y3mxJixFs2Cj8hkQhulQKg==
X-Google-Smtp-Source: AOwi7QBhmEh3xmc8h516Ov9CsJ1aMT25fb9ZTSL32cFZPi8kzAQG6engZt5fNVrPClNafZ6Wj/e7hA==
X-Received: by 10.200.44.167 with SMTP id 36mr13214369qtw.285.1505272448176; Tue, 12 Sep 2017 20:14:08 -0700 (PDT)
Received: from [10.0.30.153] (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id m31sm6826358qtf.55.2017.09.12.20.14.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Sep 2017 20:14:07 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <25E28EFD-DF13-42F1-A872-400CC1CFBBF9@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0375AFE3-9368-4F59-B926-9E9DEABA84C6"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 12 Sep 2017 23:14:06 -0400
In-Reply-To: <20170913030645.946E8855120E@rock.dv.isc.org>
Cc: dnsop WG <dnsop@ietf.org>
To: Mark Andrews <marka@isc.org>
References: <20170913021529.2540.qmail@ary.lan> <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com> <20170913030645.946E8855120E@rock.dv.isc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AbJcQbgAl0OA2x0ZoVYRyg5EpIo>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 03:14:10 -0000

--Apple-Mail=_0375AFE3-9368-4F59-B926-9E9DEABA84C6
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Sep 12, 2017, at 11:06 PM, Mark Andrews <marka@isc.org> wrote:
> Oh sorry you can't use SRV with localhost to assign a port to this
> protocol THAT HAS NO DEFAULT PORT and only a NAME.  Is this what you
> REALLY want to do?

Yes.


--Apple-Mail=_0375AFE3-9368-4F59-B926-9E9DEABA84C6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 12, 2017, at 11:06 PM, Mark Andrews &lt;<a =
href=3D"mailto:marka@isc.org" class=3D"">marka@isc.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Oh sorry you can't =
use SRV with localhost to assign a port to this</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">protocol THAT HAS NO DEFAULT PORT and only a =
NAME. &nbsp;Is this what you</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">REALLY want to =
do?</span></div></blockquote></div><br class=3D""><div =
class=3D"">Yes.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_0375AFE3-9368-4F59-B926-9E9DEABA84C6--


From nobody Wed Sep 13 01:20:25 2017
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 201331341F6 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 01:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 nCnOAYkxKMrY for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 01:20:22 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDDB1341F5 for <dnsop@ietf.org>; Wed, 13 Sep 2017 01:20:22 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id C9F0B6A3DF; Wed, 13 Sep 2017 10:20:20 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id 580766A336; Wed, 13 Sep 2017 10:20:18 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59b8ea41-034f-7f000001272a-7f0000018013-1 for <multiple-recipients>; Wed, 13 Sep 2017 10:20:17 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id 942F86A267; Wed, 13 Sep 2017 10:20:17 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id 886FF3C10C0; Wed, 13 Sep 2017 10:20:17 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYZtoYOAKNSu; Wed, 13 Sep 2017 10:20:17 +0200 (CEST)
Received: from [192.168.0.20] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 6BEEA3C01CC; Wed, 13 Sep 2017 10:20:17 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Wed, 13 Sep 2017 10:20:45 +0200
Message-ID: <153C19CC-3120-466A-A158-A9833A2D17A1@powerdns.com>
In-Reply-To: <20170913021529.2540.qmail@ary.lan>
References: <20170913021529.2540.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.7r5412)
Content-Transfer-Encoding: quoted-printable
X-purgate-ID: 151428::1505290818-0000034F-ED23E119/0/0
X-purgate-type: clean
X-purgate-size: 1271
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/R4WjCBazGpVBFDx5cv0KRWs_Gs8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 08:20:24 -0000

Hello John,

On 13 Sep 2017, at 4:15, John Levine wrote:

> In article <63DA2E77-8507-4F25-8684-14EABF9A530E@powerdns.com> you=20
> write:
>> Since we are doing a draft/RFC on what localhost is and is not, I
>> suggest we put some text in there banning (MUST NOT) the practice of
>> having localhost entries (at least those pointing to 127.0.0.1/::1?)=20
>> in
>> auth zones. If there is agreement on this I am happy to contribute=20
>> text.
>> This may mean having to say we are updating RFC 1912.
>
> Believe it or not, there are real non-loopback localhost domain names,
> like localhost.reddit.com.

That=E2=80=99s why I had (at least ..) in there. Non-loopback localhost n=
ames=20
are not a problem, unless, perhaps via search lists, they confuse=20
browsers into wrong trust levels.

> I agree that localhost.<foo> pointing to loopback is generally asking
> for trouble, but I am not at this point sufficiently confident that it
> is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
> can for example imagine ways that might make some kinds of debugging
> easier.

I would settle for SHOULD NOT. Can you elaborate on the debugging?

Kind regards,
--=20
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Wed Sep 13 02:28:36 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C606F1332E3; Wed, 13 Sep 2017 02:28:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150529490877.30471.1398903711764491836@ietfa.amsl.com>
Date: Wed, 13 Sep 2017 02:28:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/p9OH00rtbsLjIXJI_Euo777rETw>
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-session-signal-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 09:28:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

        Title           : DNS Stateful Operations
        Authors         : Ray Bellis
                          Stuart Cheshire
                          John Dickinson
                          Sara Dickinson
                          Allison Mankin
                          Tom Pusateri
	Filename        : draft-ietf-dnsop-session-signal-04.txt
	Pages           : 32
	Date            : 2017-09-13

Abstract:
   This document defines a new DNS Stateful Operation OPCODE used to
   communicate operations within persistent stateful sessions, expressed
   using type-length-value (TLV) syntax, and defines an initial set of
   TLVs used to manage session timeouts and termination.  This mechanism
   is intended to reduce the overhead of existing "per-packet" signaling
   mechanisms with "per-message" semantics as well as defining new
   stateful operations not defined in EDNS(0).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-session-signal/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnsop-session-signal-04
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-session-signal-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-session-signal-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 13 02:31:20 2017
Return-Path: <sara@sinodun.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E70132F2C for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 arLB3GXgXD60 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:31:16 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ED2D1321A7 for <dnsop@ietf.org>; Wed, 13 Sep 2017 02:31:16 -0700 (PDT)
Received: from [2001:b98:204:102:fffa::1b] (port=62849) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <sara@sinodun.com>) id 1ds40o-0002vP-El for dnsop@ietf.org; Wed, 13 Sep 2017 10:31:14 +0100
From: Sara Dickinson <sara@sinodun.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 13 Sep 2017 10:31:12 +0100
References: <150529490877.30471.1398903711764491836@ietfa.amsl.com>
To: IETF DNSOP WG <dnsop@ietf.org>
In-Reply-To: <150529490877.30471.1398903711764491836@ietfa.amsl.com>
Message-Id: <589151E0-B652-4929-830E-3F10969B81D5@sinodun.com>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FGnmoE5NuwDX5Cafr9-56A-XmSo>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-session-signal-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 09:31:18 -0000

Hi All,=20

Based on the discussions at IETF 99 and on the list this update to the =
draft makes a number of changes:

* The Title of the draft has been changed to =E2=80=98DNS Stateful =
Operations=E2=80=99 (DSO) to reflect the fact that the TLV format is not =
limited to being used for signalling
* The draft now updates RFC1035
* The term 'DSO session=E2=80=99 is used throughout for clarity
* A paragraph has been added to the Introduction to discuss the use of a =
new format
* Several terms in the Terminology section have been updated and some =
new ones added
* Clarified the use of the words timer and timeout throughout the =
document
* A short discussion section has been added with specific use cases
* The specific mention of QUIC has been removed, the text now just =
describe the properties of the transport used for DSO.=20
* The text has been updated to specify that messages must be processed =
in the order they were sent (not received)
* A modifier Encrypted Padding TLV has been added to support padding of =
encrypted queries
* The text describing the behaviour of middle-boxes has been updated
* The set of RCODES defined in the document has been extended
* Responses to DSO messages are now optional: An Acknowledgement bit has =
been added to the DSO data format which specifies if the DSO message =
requires an acknowledgement response
* A section has been added to specify exactly what a client should to =
with the timers/timeouts when receiving a Keepalive TLV
* The section on Connection sharing is now consistent with RFC7766

Regards

Sara.=20

> On 13 Sep 2017, at 10:28, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Domain Name System Operations WG of =
the IETF.
>=20
>        Title           : DNS Stateful Operations
>        Authors         : Ray Bellis
>                          Stuart Cheshire
>                          John Dickinson
>                          Sara Dickinson
>                          Allison Mankin
>                          Tom Pusateri
> 	Filename        : draft-ietf-dnsop-session-signal-04.txt
> 	Pages           : 32
> 	Date            : 2017-09-13
>=20
> Abstract:
>   This document defines a new DNS Stateful Operation OPCODE used to
>   communicate operations within persistent stateful sessions, =
expressed
>   using type-length-value (TLV) syntax, and defines an initial set of
>   TLVs used to manage session timeouts and termination.  This =
mechanism
>   is intended to reduce the overhead of existing "per-packet" =
signaling
>   mechanisms with "per-message" semantics as well as defining new
>   stateful operations not defined in EDNS(0).
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-session-signal/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-session-signal-04
> =
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-session-signal-04
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-session-signal-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Wed Sep 13 02:56:23 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2E01332E3 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.833
X-Spam-Level: 
X-Spam-Status: No, score=-0.833 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=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 byuf9L5KrAKQ for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:56:17 -0700 (PDT)
Received: from smtpbg320.qq.com (smtpbg320.qq.com [14.17.32.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA96A133018 for <dnsop@ietf.org>; Wed, 13 Sep 2017 02:56:16 -0700 (PDT)
X-QQ-mid: bizesmtp8t1505296547txomko7yl
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Wed, 13 Sep 2017 17:55:45 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: pTE/Q6TrPPc2iMz88JBtg+TfsXP1pBnuHok7a63KK2VDB8Wuh61oOABp69ekj 5wPYQdLiiLCE9IdE4PRmqbDzqTBMM17smJBRSd3CgZ22QAayfUzg+cTivaBG7ReiWIEY26b wsuXwEhxPlp9/Lrvz9/rkjjEYOrsY00p8bpVkEz3Wv4h2nrjPsoWw56WpGG+oAHR49f6Ofj 9ZXFk6u0H77sPMmDhbrvYAKv1BqnMWvJT/aFReRkxfJ+mE+53I8ZdGyHrB6IUDClFahg176 895aUVDV4GvcieqM6t/+BAcqsMGkkw9R+NdA==
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'Lanlan Pan'" <abbypan@gmail.com>, "'Davey Song'" <songlinjian@gmail.com>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com>
In-Reply-To: <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com>
Date: Wed, 13 Sep 2017 17:55:46 +0800
Message-ID: <004101d32c76$79de2100$6d9a6300$@cn>+0D046F6E47FECD60
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdMrrKSd0XpT790VRJy3er4CeK+KDQAya/zg
Content-Language: zh-cn
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgweb:qybgweb1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YG5MBie72Lgqo304LPb_sqfCey8>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgRndkOiBJLUQgQWN0aW9uOiBkcmFmdC1z?= =?utf-8?q?ong-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 09:56:21 -0000

> ATR make Authoritative Servers send normal big response packet before =
they try to send TC response for large RRsets ?=20

No. big response packet first, then TC response.

Davey


From nobody Wed Sep 13 02:58:35 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C92A1341F7 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.333
X-Spam-Level: 
X-Spam-Status: No, score=-1.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 PQiiPShEbXln for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 02:58:29 -0700 (PDT)
Received: from smtpbg328.qq.com (smtpbg328.qq.com [14.17.43.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40D71132713 for <dnsop@ietf.org>; Wed, 13 Sep 2017 02:58:29 -0700 (PDT)
X-QQ-mid: bizesmtp13t1505296685tji3o1xl
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Wed, 13 Sep 2017 17:58:04 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: K5r71nzN+ONCwwuR/LHg3MQjmj6Nu9AdaoJs+oonSPUsIRacS6HhlOvMncfX3 lHnMbMZIScv549Z/F1faaMiWhaBgIBnyNchhmnU4cCn3w6KcU43DB4FXn7746ljP/4U8W4B mxiYXubWotEQs+Qi8zfp2SneTOPigi5dIO82nuJcw92iqYUu50Uik34NZ/OrugdWfnsxSn/ T1eiCB3RNhwXa47mDi3n3y+nz0EsyPI+R1qTwuV9c53Rsm/QilVmVrEcQAjQCe191s2A/UQ B0dJEUtqlchlYlHWePWln2KeEkIEYsoaGCXC1E0fz/KQUHBj5Hcwkd14Q=
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'Lanlan Pan'" <abbypan@gmail.com>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com> 
In-Reply-To: 
Date: Wed, 13 Sep 2017 17:58:05 +0800
Message-ID: <004201d32c76$ccac3fc0$6604bf40$@cn>+B65255D60F568E23
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdMrrKSd0XpT790VRJy3er4CeK+KDQAya/zgAAAafQA=
Content-Language: zh-cn
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgweb:qybgweb19
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FuP_kn9e0AEOkPGj0b0389mSRV0>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgRndkOiBJLUQgQWN0aW9uOiBkcmFmdC1z?= =?utf-8?q?ong-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 09:58:33 -0000

Sorry, You are right.

> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) =
[mailto:ljsong@biigroup.cn]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2017=E5=B9=B49=E6=9C=8813=E6=97=A5 17:56
> =E6=94=B6=E4=BB=B6=E4=BA=BA: 'Lanlan Pan'; 'Davey Song'
> =E6=8A=84=E9=80=81: 'dnsop'
> =E4=B8=BB=E9=A2=98: =E7=AD=94=E5=A4=8D: [DNSOP] Fwd: I-D Action: =
draft-song-atr-large-resp-00.txt
>=20
>=20
> > ATR make Authoritative Servers send normal big response packet =
before they
> try to send TC response for large RRsets ?
>=20
> No. big response packet first, then TC response.
>=20
> Davey


From nobody Wed Sep 13 06:49:27 2017
Return-Path: <rharolde@umich.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6FF5132320 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 06:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 GPWF28IJChln for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 06:49:13 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C6A133041 for <dnsop@ietf.org>; Wed, 13 Sep 2017 06:49:13 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id q80so654789ywg.2 for <dnsop@ietf.org>; Wed, 13 Sep 2017 06:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9H1NBy9R2MlkfEv7K304j1S9zZOzsh5H4vdZ4NyrulQ=; b=qPl1oh/lbBQdXQBVyqXk2+zuKTQWn7hx6WzWew3DX/Zq7lap0t7NDSp5YSZnohYeN6 8VIQzyXsecP2QnqJjD/Wa0+HID7NoCOGxo+wpvJDR+U+/kGch1HdRY4rwM7o6HZrIVcX 1AEzmpiiT1mGxefU0fFLDxrcyQY30rCRXKDCBkiIvh7oHcfdt98SLy8aHoIcVWMkwgQc uz8ytZVuncZiYHM7mvqC9COvBmMz86S036wJ4abU6Lmk2at5k+M8ymjmwBiAM1zFzWb1 y7NE4akrsHpvjFAyvDJ1fd9j3ORZnfQBTrjiiKGDdRmE/IB1cW48cm8Uml3ZGhXHFdLI 4C0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9H1NBy9R2MlkfEv7K304j1S9zZOzsh5H4vdZ4NyrulQ=; b=t4roiD+GP6TYw9Qt2zuOK+rzczmBm7WKZ0w65ZAta3H2Ygdakyt5cN+n5K0LcA+B4D PExlsruvMSbu+a5QaAgrYiqWL0WB8RonFSb4wjrxbJxIo8aGeLKJHNgy5Pwlklr70WDi T3mdAq4+Z/MVywuEolPwogYMlpYzmHY9O1VWpycSKGYxXZ1Z6SIh/DoDSsR3GeI1S/iw 3EM8OMIz/07bnNr1JecEpa9RbKB/z4rvlDxrAW3WYl3U2JxsH1NP5cC+Djk+c7W4jAr/ Wg8IdHhm2n3hN/gQR11o6KoFnTRjh7VCmwotdfKZbIsY4863jkHyc8MSgML8rHu1m6Gl bxJg==
X-Gm-Message-State: AHPjjUjSwWWXo0EiI6RT06jnDvA3fWG0RzLXNpEMsEfTogczG3HnMKZS 6kyTwap9BiEz6aiCParF+DJvge8C3xDUf24bey+5iQ==
X-Google-Smtp-Source: ADKCNb7TqGcutwf7fuXwFBTYgfPInvvDrO5po7H84OfAbHsZT44/ksfSpsioaG+dq2dXhM5/uI8iv3maqCBDB4ANF20=
X-Received: by 10.37.6.69 with SMTP id 66mr6645508ybg.19.1505310552533; Wed, 13 Sep 2017 06:49:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.118.16 with HTTP; Wed, 13 Sep 2017 06:49:11 -0700 (PDT)
In-Reply-To: <150525870106.30485.18179687243292311597@ietfa.amsl.com>
References: <150525870106.30485.18179687243292311597@ietfa.amsl.com>
From: Bob Harold <rharolde@umich.edu>
Date: Wed, 13 Sep 2017 09:49:11 -0400
Message-ID: <CA+nkc8DT4jYE6=jgvN5GcRm+X4JBTGnSmv75DDLcrgXveG9h1w@mail.gmail.com>
To: internet-drafts@ietf.org
Cc: i-d-announce@ietf.org, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113b35ccc2d3200559126c46"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yGHU5XTQhZkpSnCzKEP1j5VRc8g>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 13:49:26 -0000

--001a113b35ccc2d3200559126c46
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 12, 2017 at 7:25 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations WG of the
> IETF.
>
>         Title           : Security Considerations for RFC5011 Publishers
>         Authors         : Wes Hardaker
>                           Warren Kumari
>         Filename        : draft-ietf-dnsop-rfc5011-
> security-considerations-03.txt
>         Pages           : 13
>         Date            : 2017-09-12
>
> Abstract:
>    This document extends the RFC5011 rollover strategy with timing
>    advice that must be followed in order to maintain security.
>    Specifically, this document describes the math behind the minimum
>    time-length that a DNS zone publisher must wait before signing
>    exclusively with recently added DNSKEYs.  This document also
>    describes the minimum time-length that a DNS zone publisher must wait
>    after publishing a revoked DNSKEY before assuming that all active
>    RFC5011 resolvers should have seen the revocation-marked key and
>    removed it from their list of trust anchors.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc5011-
> security-considerations/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-rfc5011-
> security-considerations-03
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc5011-security-
> considerations-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-rfc5011-
> security-considerations-03
>
>
>
5.1.1.  Attack Timing Breakdown

"T+11 through T-29"

"T-29" should be "T+29"

-- 
Bob Harold

--001a113b35ccc2d3200559126c46
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure"><br></div></div><div class=3D"gmail_quote">On Tue, Sep 12, 2017 at 7:2=
5 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" ta=
rget=3D"_blank">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Domain Name System Operations WG of the IE=
TF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Security Considerations for RFC5011 Publishers<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Wes =
Hardaker<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Warren Kumari<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-dnsop-rfc5011-<wbr>security-considerations-03.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 13<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-09-12<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document extends the RFC5011 rollover strategy with timin=
g<br>
=C2=A0 =C2=A0advice that must be followed in order to maintain security.<br=
>
=C2=A0 =C2=A0Specifically, this document describes the math behind the mini=
mum<br>
=C2=A0 =C2=A0time-length that a DNS zone publisher must wait before signing=
<br>
=C2=A0 =C2=A0exclusively with recently added DNSKEYs.=C2=A0 This document a=
lso<br>
=C2=A0 =C2=A0describes the minimum time-length that a DNS zone publisher mu=
st wait<br>
=C2=A0 =C2=A0after publishing a revoked DNSKEY before assuming that all act=
ive<br>
=C2=A0 =C2=A0RFC5011 resolvers should have seen the revocation-marked key a=
nd<br>
=C2=A0 =C2=A0removed it from their list of trust anchors.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc5011-securi=
ty-considerations/" rel=3D"noreferrer" target=3D"_blank">https://datatracke=
r.ietf.org/<wbr>doc/draft-ietf-dnsop-rfc5011-<wbr>security-considerations/<=
/a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-dnsop-rfc5011-security-co=
nsiderations-03" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.or=
g/html/<wbr>draft-ietf-dnsop-rfc5011-<wbr>security-considerations-03</a><br=
>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc5011-s=
ecurity-considerations-03" rel=3D"noreferrer" target=3D"_blank">https://dat=
atracker.ietf.org/<wbr>doc/html/draft-ietf-dnsop-<wbr>rfc5011-security-<wbr=
>considerations-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dnsop-rfc5011-sec=
urity-considerations-03" rel=3D"noreferrer" target=3D"_blank">https://www.i=
etf.org/rfcdiff?<wbr>url2=3Ddraft-ietf-dnsop-rfc5011-<wbr>security-consider=
ations-03</a><br>
<br><br></blockquote><div><br></div><div>5.1.1.=C2=A0 Attack Timing Breakdo=
wn</div></div></div><blockquote style=3D"margin:0 0 0 40px;border:none;padd=
ing:0px"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>&quot;T=
+11 through T-29&quot;</div></div></div></blockquote><div class=3D"gmail_ex=
tra"><div class=3D"gmail_quote"><div>&quot;T-29&quot; should be &quot;T+29&=
quot;</div><div><br></div><div>--=C2=A0</div><div>Bob Harold</div><div><br>=
</div></div><br></div></div>

--001a113b35ccc2d3200559126c46--


From nobody Wed Sep 13 09:34:22 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A31132C32 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 07p66oJ-f-AK for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:34:19 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C4761321B6 for <dnsop@ietf.org>; Wed, 13 Sep 2017 09:34:18 -0700 (PDT)
Received: (qmail 50017 invoked from network); 13 Sep 2017 16:34:17 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 13 Sep 2017 16:34:17 -0000
Date: 13 Sep 2017 16:33:55 -0000
Message-ID: <20170913163355.1038.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: peter.van.dijk@powerdns.com
In-Reply-To: <153C19CC-3120-466A-A158-A9833A2D17A1@powerdns.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Q2PLEU1PbPbdolh53-bOcq-zL6E>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 16:34:21 -0000

In article <153C19CC-3120-466A-A158-A9833A2D17A1@powerdns.com> you write:
>> I agree that localhost.<foo> pointing to loopback is generally asking
>> for trouble, but I am not at this point sufficiently confident that it
>> is never ever a good idea to say MUST NOT rather than SHOULD NOT.  I
>> can for example imagine ways that might make some kinds of debugging
>> easier.
>
>I would settle for SHOULD NOT. Can you elaborate on the debugging?

There is something strange going on with my remote server, and I use
localhost.mydomain so a little debugging server on my own computer
can steal state and see whats going on.

On the other hand, I could do this just as well:

gazornplotz.mydomain IN A 127.0.0.1

so never mind.  Still not sure I haven't missed something, though.

R's,
John


From nobody Wed Sep 13 09:46:55 2017
Return-Path: <matt@conundrum.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D76B41321B6 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.com
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 rnGV-GUk7GUN for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 09:46:52 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 629EF126D0C for <dnsop@ietf.org>; Wed, 13 Sep 2017 09:46:50 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id v19so3990925ite.0 for <dnsop@ietf.org>; Wed, 13 Sep 2017 09:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yWnyO1uBnVV3BwZcMTqjgu/ln0oAHPQFORldALERGsk=; b=QRvRudbvo0vr0uNWrp4Y6dRsUyh8y1q3+/teoGcSbFrJQCoIqDeXwcsq1quy3c3WjL Ekccxixx+11bmC1EuVMUSMRTvaFd8eCeVs0gttmCa/mlMr3zNQQOY29gBI0Gb3AiODib axYrmSTPdptmn+YnCZ61zvuyHctvAn/kYhechLCODbQRe29GjERBH8/c+1I34iWLpkfV oRUNygoUyeUX8xRiavRIGJ/oOKhhRfgUg9a25Rpg5yqeCNMZo+pnuq/VffHBTU/3EQDO fu6WgkPHsOyJXJdrSWeTYB3im3+hafqO12VSsDYNi83GwRLYH+lPqJSFPHnYF6y96upE 0qbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yWnyO1uBnVV3BwZcMTqjgu/ln0oAHPQFORldALERGsk=; b=Zd4dTTZx36wVvNIQH+6pVXz0FWURPc38mlHk/cCf2mClP/i+NsXtj39pTv0InGNjBp xANJq602qGYNH3ZAuM4vKDTpQjl/uiJLtnTWfveQ9lAoiy1j0cxHl9zKUiRWCxqTimzw 5RETTH8liOtGpVJIUaMOCB3Zf1ylYkdNSHL7Fae7IHh9+s51Ive5OiyvWLzGFS9uKKcB Czgp4Ptn5ewwbIdNPeS5l++AClVsVCFzFlyvhxj0Y7cU55T4R4r6k1joad/RmMMgq3U1 2ZhD9PPjOxookTW/ESeP/OsAwDy9WmxEuhFB5aoKvn/cIeOHasEFVYBz7jKnL/5MzoXs 35sA==
X-Gm-Message-State: AHPjjUh4bNUPzJuUV6ibnIg5A3Rwh6j2h+Th5yjaLloaqhkf83kkHcA5 mwTzy+1RIHJUBFL8xlIz7hjCTVIQFC17q+kIhIGZAw==
X-Google-Smtp-Source: AOwi7QDeA+XKbn5CBeKyyFSMmXaTa244QOR6zGW0UpEFZGfngi4UM8IWLsVYYHNAwn3ZAU3yI/IxA8meFXEiiOkGxAk=
X-Received: by 10.36.181.73 with SMTP id j9mr1166494iti.6.1505321210367; Wed, 13 Sep 2017 09:46:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.20.136 with HTTP; Wed, 13 Sep 2017 09:46:49 -0700 (PDT)
In-Reply-To: <25E28EFD-DF13-42F1-A872-400CC1CFBBF9@fugue.com>
References: <20170913021529.2540.qmail@ary.lan> <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com> <20170913030645.946E8855120E@rock.dv.isc.org> <25E28EFD-DF13-42F1-A872-400CC1CFBBF9@fugue.com>
From: Matthew Pounsett <matt@conundrum.com>
Date: Wed, 13 Sep 2017 09:46:49 -0700
Message-ID: <CAAiTEH9QwgC-aSPf2KZPOcQtZVmTRZek5OcbXTt-N+BOcCM=Zg@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Mark Andrews <marka@isc.org>, dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d9e42048075055914e881"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ath0tnDPs-RiMMOUDAJ19c9V5fc>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 16:46:54 -0000

--f403045d9e42048075055914e881
Content-Type: text/plain; charset="UTF-8"

On 12 September 2017 at 20:14, Ted Lemon <mellon@fugue.com> wrote:

> On Sep 12, 2017, at 11:06 PM, Mark Andrews <marka@isc.org> wrote:
>
> Oh sorry you can't use SRV with localhost to assign a port to this
> protocol THAT HAS NO DEFAULT PORT and only a NAME.  Is this what you
> REALLY want to do?
>
>
> Yes.
>
> I thought the goal was to ensure that localhost names map to loopback.

--f403045d9e42048075055914e881
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 12 September 2017 at 20:14, Ted Lemon <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><span class=3D"">On Sep 12, 2017, at 11:06 PM, Mark Andrews &lt;<a hr=
ef=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt; wrote:<=
div><blockquote type=3D"cite"><div><span style=3D"font-family:Menlo-Regular=
;font-size:18px;font-style:normal;font-variant-caps:normal;font-weight:norm=
al;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:no=
ne;white-space:normal;word-spacing:0px;float:none;display:inline!important"=
>Oh sorry you can&#39;t use SRV with localhost to assign a port to this</sp=
an><br style=3D"font-family:Menlo-Regular;font-size:18px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px"><span style=3D"font-family:Menlo-Regular;font-size:18px;font-style:no=
rmal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;white-space:normal;word-sp=
acing:0px;float:none;display:inline!important">protocol THAT HAS NO DEFAULT=
 PORT and only a NAME.=C2=A0 Is this what you</span><br style=3D"font-famil=
y:Menlo-Regular;font-size:18px;font-style:normal;font-variant-caps:normal;f=
ont-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px"><span style=3D"font-=
family:Menlo-Regular;font-size:18px;font-style:normal;font-variant-caps:nor=
mal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0=
px;text-transform:none;white-space:normal;word-spacing:0px;float:none;displ=
ay:inline!important">REALLY want to do?</span></div></blockquote></div><br>=
</span><div>Yes.</div><div><br></div></div></blockquote><div>I thought the =
goal was to ensure that localhost names map to loopback. =C2=A0=C2=A0</div>=
</div><br></div></div>

--f403045d9e42048075055914e881--


From nobody Wed Sep 13 09:51:36 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2991A132D7B; Wed, 13 Sep 2017 09:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 zHbtrMY1G5NO; Wed, 13 Sep 2017 09:51:33 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 190F6132D54; Wed, 13 Sep 2017 09:51:33 -0700 (PDT)
Received: from localhost (50-1-20-198.dsl.static.fusionbroadband.com [50.1.20.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 88CFB244D2; Wed, 13 Sep 2017 09:51:32 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Bob Harold <rharolde@umich.edu>
Cc: internet-drafts@ietf.org, IETF DNSOP WG <dnsop@ietf.org>, i-d-announce@ietf.org
References: <150525870106.30485.18179687243292311597@ietfa.amsl.com> <CA+nkc8DT4jYE6=jgvN5GcRm+X4JBTGnSmv75DDLcrgXveG9h1w@mail.gmail.com>
Date: Wed, 13 Sep 2017 09:51:31 -0700
In-Reply-To: <CA+nkc8DT4jYE6=jgvN5GcRm+X4JBTGnSmv75DDLcrgXveG9h1w@mail.gmail.com> (Bob Harold's message of "Wed, 13 Sep 2017 09:49:11 -0400")
Message-ID: <yblvakma6ek.fsf@wu.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PielhQGxfdc6O3AblkKpMrXdnZc>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 16:51:34 -0000

Bob Harold <rharolde@umich.edu> writes:

> "T-29" should be "T+29"

Good catch; thank you! 
-- 
Wes Hardaker
USC/ISI


From nobody Wed Sep 13 10:01:25 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57EDC132D7B for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 tFfIkZVA2MA9 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:01:16 -0700 (PDT)
Received: from mail.hardakers.net (unknown [168.150.236.43]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866D41323B8 for <dnsop@ietf.org>; Wed, 13 Sep 2017 10:01:16 -0700 (PDT)
Received: from localhost (50-1-20-198.dsl.static.fusionbroadband.com [50.1.20.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 195EA244D2 for <dnsop@ietf.org>; Wed, 13 Sep 2017 10:01:16 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: dnsop@ietf.org
Date: Wed, 13 Sep 2017 10:01:15 -0700
Message-ID: <yblmv5ya5yc.fsf@wu.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dXHOzftd7Cd8ofpAIHosHkeYjho>
Subject: [DNSOP] Responding to MSJ review of the previous rfc5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 17:01:23 -0000

Mike, after your lengthy last review I went through and carefully made
sure each of your comments were considered.  Most resulted in changes, a
few seemed to be just comments and there was nothing to do, and two we
didn't think were correct.  Below is the summary of the changes in the
most recent version based on your review from July.

Wes Hardaker


Table of Contents
_________________

1 Notes / Edits from Mike StJohn on <2017-07-06 Thu>
.. 1.1 ACCEPTED Use "exclusively" rather than "only" where you can - "only" has
.. 1.2 ACCEPTED In the introduction  - "validators can update" vs "validators can
.. 1.3 ACCEPTED In the introduction - same issue with "only recently"
.. 1.4 ACCEPTED In the introduction - "ceasing publication of a revoked key" vs
.. 1.5 FIXED Section 1.1 - What is the definition of "rolled"?   Your use of it
.. 1.6 FIXED Section 2 "which apply to" vs "as required from".
.. 1.7 FIXED Section 2 "Note that it does not..." - which "it" are you talking about?
.. 1.8 ACCEPTED Section 2 "using only recently" - same issue as above.
.. 1.9 ACCEPTED Section 2. New para at "Failure of a DNSKEY..."
.. 1.10 ACCEPTED Section 2. "... leaving that key in their trust anchor storage
.. 1.11 ACCEPTED Section 3: Attacker.  "An entity intent..." vs "An attacker
.. 1.12 FIXED Section 4.1:  This doesn't actually describe what's in 5011 -
.. 1.13 ACCEPTED Section 4.1, bullet 3:  Same problem with "only".  Instead "Begin
.. 1.14 REJECTED Section 4.2 last para:  This is only an attack if the private key
.. 1.15 REJECTED Section 6 - general comment.   You're doing interval calculations
.. 1.16 FIXED Section 5.1.1 - You're missing a *very* important point here -
.. 1.17 NOTHINGTODO Section 5.1.1 doesn't actually apply if you use the 5011 rollover
.. 1.18 FIXED Section 5.1.1, T+35:  "since the hold down time of 30 days + 1/2
.. 1.19 NOTHINGTODO Section 6 - the formulas are wrong.  I also  don't understand
.. 1.20 NOTHINGTODO The final formula should be:
.. 1.21 NOTHINGTODO In any event, the point needs to be made that this attack
.. 1.22 FIXED The value in 6 regardless of what it is is the wrong value for


1 Notes / Edits from Mike StJohn on <2017-07-06 Thu>
====================================================

1.1 ACCEPTED Use "exclusively" rather than "only" where you can - "only" has
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  some issues with misunderstanding.  E.g. in the abstract you have
  "only recently" which can be interpreted applying to "recently" rather
  than meaning "exclusively" with " recently added DNSKEYs"


  Instead in the abstract: "... before exclusively signing with recently
  added DNSKEYs"

  + Result: I don't object to the wording change, so I made it.  I don't
    think it was needed as only is pretty concrete in understanding
    everywhere I've seen it.


1.2 ACCEPTED In the introduction  - "validators can update" vs "validators can
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  extend".

  + Result:


1.3 ACCEPTED In the introduction - same issue with "only recently"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + Result:


1.4 ACCEPTED In the introduction - "ceasing publication of a revoked key" vs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  "removing a key from a zone"

  + Result:


1.5 FIXED Section 1.1 - What is the definition of "rolled"?   Your use of it
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  doesn't match 5011s and it's not defined either here or in 4033 or .
  Also "before signing a zone" - I don't think this is exactly what you
  asked them and the summary is probably inaccurate.

  + Result: rolled -> introduced
  + Result: added "exclusively" to fix the other aspect


1.6 FIXED Section 2 "which apply to" vs "as required from".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + Result: to just "from" as the other words are more confusing


1.7 FIXED Section 2 "Note that it does not..." - which "it" are you talking about?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + Result: "this document"


1.8 ACCEPTED Section 2 "using only recently" - same issue as above.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + Result:


1.9 ACCEPTED Section 2. New para at "Failure of a DNSKEY..."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + Result:


1.10 ACCEPTED Section 2. "... leaving that key in their trust anchor storage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  beyond the key's expected lifetime." vs "... leaving a key in their
  trust anchor storage beyond their expected lifetime" -"their" applies
  to two different things

  + Result:


1.11 ACCEPTED Section 3: Attacker.  "An entity intent..." vs "An attacker
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  intent..." - self referencing definition problem

  + Result:


1.12 FIXED Section 4.1:  This doesn't actually describe what's in 5011 -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  specifically bullet 3 was modified to clarify your concerns, but isn't
  what was in 5011.  You need to have both here.

  + Result: Intro paragraph added to note we're paraphrasing 5011 at a
    very high level only.


1.13 ACCEPTED Section 4.1, bullet 3:  Same problem with "only".  Instead "Begin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  to exclusively use recently published DNSKEYs..."

  + Result:


1.14 REJECTED Section 4.2 last para:  This is only an attack if the private key
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  is compromised.  In which case, with only a steady state of a single
  key, you've got lots of other problems.  Basically, in your one in one
  out with a steady state of one model, once the current private key is
  compromised you have no ability to fix the problem.  But getting the
  numbers for figuring out when this change becomes "sticky" correct is
  useful.

  + Result: I disagree.  The attack is not just about reusing the stale
    key beyond it's life time.  The attack in this document describes
    the ability to affect the state of the validator so that it's state
    doesn't match the desired state of the Trust Anchor Publisher.
    You're right, that having that state be out of sync isn't useful to
    an attacker until they can break the key for the trust anchor.  But
    an attacker performing this "old state" attack means they have years
    and years to potentially break the key and introduce fake data into
    the dns zone years potentially years the future.  But in the end,
    this *is* an attack against the state of the validator, just not of
    the severity you allude to above.


1.15 REJECTED Section 6 - general comment.   You're doing interval calculations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  and you want to do date/time wall clock calculations instead.  While
  the 5011 values are based on intervals from the RRs get to the
  validator, the publisher has to be looking at absolute times first
  (e.g. signature inception and expiration, original TTL) and then
  deltas from those. [Note, this is NOT a new comment - I've made it
  previously and strongly]

  + Result: You've failed to convince me the text needs to change.
    Please propose exact wording (or at least an example) that you feel
    better serves the purpose.  The wall clock and the interval are
    mutatable between each other.  We are calculating the interval to
    wait beyond the publication point (waitTime) which is the same as
    wallclock_now + waitTime.

  + That being said, I changed the intro text a bit to be a bit more
    clear about the fact it starts from the publication time.

    + Based on the conversation in Prague, I'll leave it as is but try
      to clarify a bit about the issue.


1.16 FIXED Section 5.1.1 - You're missing a *very* important point here -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  that DNSKEY RRSets may be signed ahead of their use.  You need to
  assume that once signed, they are available to be published - even by
  an attacker.  So wherever you have "signature lifetime" you want
  something like "latest signature expiration of any DNSKEY RRSet not
  containing the new key" or at least you want to calculate the
  date/time value based on that.

  + Result: There are two issues here:
    1. When we discuss the exact requirements for publication, we should
       be very very clear about the timing requirements.  I agree.
    2. We're trying to pass on the concept of the attack in this
       section, not necessarily a description that exactly covers all
       possibilities.  So, though I'm all for making it as accurate as
       we can, I don't think we should make the example text so
       confusing to cover all the corner cases that no one can follow
       it.
    3. It doesn't benefit an attacker to publish the signatures ahead of
       time. So you're right that anyone can publish new signatures, it
       really doesn't affect the timing required by the publisher to
       wait, which is the point of this draft.
    4. The important take away I take from your text is that any delay
       between signing and publication will affect the length of time to
       wait, and I'm sure this is what you mean by needing to calculate
       via wall-clock (since everything should be based on
       sigexpiration).

  XXX: With this goal in mind, I've cleaned up the text a bit to make it
  a bit more clear.


1.17 NOTHINGTODO Section 5.1.1 doesn't actually apply if you use the 5011 rollover
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  approach (section 6.3).  E.g. K_old (and any RRSets it signed) will be
  revoked the first time K_new is seen and K_standby is the signing key.
  At this point this reduces to a normal denial of service attack (where
  you prevent new data from being retrieved by the resolver).  You'd
  need a different section to do that analysis. [And thinking about it,
  why is there any practical difference between this attack and a normal
  denial of service attack in the first place?]

  + Result: As we've both agreed in the past, the attack described in
    our 5.1.1 section only applies when you sign exclusively with a key
    that is too new.  So, yes when you are using K_standby, the attack
    in question doesn't work.  We're only describing the case where
    there either isn't a K_standby, or when K_standby is also newer than
    our 'waitTime' time.

  + And, yes by preventing a new key from being accepted as a trust
    anchor, this is a denial of service attack.  Though one with
    potentially serious ramifications since it may require manual
    intervention on all the devices affected by it (unlikely a
    network-based DDoS attack, it doesn't stop when the attacker stops
    sending packets; this is long lived until the configuration is
    manually fixed).


1.18 FIXED Section 5.1.1, T+35:  "since the hold down time of 30 days + 1/2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  the signature validity... " - Two items: Wordsmithing: The hold down
  time is just the 30 days, not the plus 1/2...  which I *think* given
  the reference to 2.3 is actually the queryInterval. clarify please.
  And queryInterval is not actually 1/2 the signature validity - its the
  MIN (15 days, 10 days (sig life)/2 and 1 day(orig ttl)/2) or 1/2 a
  day.

  + Result: you're misreading the sentence thinking the holddown time
    includes the math with the + and onward, where the holddown time was
    only the 30 minutes.  I'll reword and though I was trying to avoid
    the much more complex math in the example, you're correct that it's
    1/2 the queryInterval which has more terms to calculate it exactly.


1.19 NOTHINGTODO Section 6 - the formulas are wrong.  I also  don't understand
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  where you got MAX(originalTTL/2,15 days) - there's no support for this
  in the text.

  You're misreading the commas.  One of the terms in the outer max
  clause is "MAX(original TTL of K_old DNSKEY RRSet) / 2".  This is
  slightly different than what is in the "1/2*OrigTTL" clause in 5011
  itself.  This is because if the publisher changes TTLs over the course
  of signing, you have to take the maximum value of any of them, not
  just the most recent.  (though, to be super-accurate you need to do
  some math which we might want to describe about when a given TTL is
  published vs when Knew is introduced).

  Anyway, in the end, the formula in ours draft directly derives from
  what is in yours.  We do take into account the possibility of multiple
  TTLs for a given signature set, which 5011 doesn't take into account
  (and to some extent, it's less important, but only further shows how
  much variance a resolver might have before accepting a new trust
  anchor).

  A clear piece of advice for an eventual BCP would be to not change
  TTLs at the same time you start any 5011 publication or revocation
  process.


1.20 NOTHINGTODO The final formula should be:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  EarliestDateWhereAttackFails::= latest SignatureExpiration of any
  DNSKEY RRSet not containing the new key

  [ ... alternate math analysis deleted for brevity ... ]

  + Result: there are multiple ways to list out the math / timing behind
    this.  You do spell out an alternate way to lay out the math; I
    believe your purpose was not to offer a replacement but to ensure we
    agree upon the timing.  I do see that you're using wall-clock type
    math, which certainly works and should be equivalent to your example
    start tiem of 5/1/2017 00:00UTC + our waitTime.

  + I do see your point that anyone could publish the data once signed,
    not just the


1.21 NOTHINGTODO In any event, the point needs to be made that this attack
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  - while real -
  is a "retail" attack that would be difficult to prosecute by a single
  attacker across a broad range of end-entities.  This goes to the
  general model that no publisher of DNS data knows each and every
  consumer of that data, nor can wait its publication on every consumer
  getting published data.  The data protocol for DNS is unidirectional
  and the update protocol in 5011 was designed with that in mind.

  + Result: We never state in the document that the attack was against
    every validator out there.  It affects only the validators that
    received replayed key sets and signatures.  We don't dive into the
    analysis of how difficult it is to achieve such a replay, either
    directly or by cache poisoning upstream resolvers, or....  That's
    outside the scope of the document.  Thus, I don't see any change to
    the text that is needed as I think the text is pretty clear that a
    replay attack is already necessary in the attack model.


1.22 FIXED The value in 6 regardless of what it is is the wrong value for
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  revocation.  revocationPublicationWaitTime is basically
  EarliestDateAttackFails + queryInterval + slop.  Revocations take
  place immediately. You can delay them only as long as you have old
  valid signed RRSets.

  + Result: wording changed to addWaitTime and remWaitTime, and math
    adjusted to drop the 30 day part of the timer.  Thanks.


-- 
Wes Hardaker
USC/ISI


From nobody Wed Sep 13 10:19:41 2017
Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3FC132C32 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 TFyvY2pdHVbs for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:19:39 -0700 (PDT)
Received: from gal.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD8D713292D for <dnsop@ietf.org>; Wed, 13 Sep 2017 10:19:38 -0700 (PDT)
Received: (qmail 58792 invoked from network); 13 Sep 2017 17:19:37 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 13 Sep 2017 17:19:37 -0000
Date: 13 Sep 2017 17:19:15 -0000
Message-ID: <20170913171915.1194.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20170913030645.946E8855120E@rock.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lUQ3v8X92JSFv7GgwfsXRV-nWxo>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 17:19:40 -0000

In article <20170913030645.946E8855120E@rock.dv.isc.org> you write:
>> When we look at edge cases like this, it's tempting to be swept away by
>> the futility of trying to close every gap.   But it's still worth closing
>> the ones we can close.   Trying to outlaw localhost.* is hopeless.  But
>> outlawing *.localhost is certainly valid and viable, and as DNSSEC
>> adoption increases, more and more it will be the case that we actually
>> need do nothing to break it.   "localhost" + search list still fails
>> unsafe.
>
>Why would we want to outlaw *.localhost?  Just because it is
>inconvient for the IAB and ICANN that they didn't address this issue
>correctly years ago.

I concur with Mark that while localhost.<foo> is a problem,
<foo>.localhost is not.  I've occasionally used that hack to pass
traffice to various servers running on 127/8 addresses other than
127.0.0.1.

R's,
John


From nobody Wed Sep 13 10:36:08 2017
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652481323F7 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 0pjUrytRCaqn for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 10:36:04 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D1051320D9 for <dnsop@ietf.org>; Wed, 13 Sep 2017 10:36:04 -0700 (PDT)
Received: from localhost (50-1-20-198.dsl.static.fusionbroadband.com [50.1.20.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 6A83824548; Wed, 13 Sep 2017 10:36:02 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Tony Finch <dot@dotat.at>
Cc: Wes Hardaker <wjhns1@hardakers.net>, John Levine <johnl@taugh.com>, dnsop@ietf.org
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk>
Date: Wed, 13 Sep 2017 10:36:02 -0700
In-Reply-To: <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> (Tony Finch's message of "Tue, 12 Sep 2017 11:41:28 +0100")
Message-ID: <yblh8w6a4cd.fsf@wu.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FnHPNMMeCZewZ6YEcoGmPwjXQq4>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 17:36:05 -0000

Tony Finch <dot@dotat.at> writes:

> From my brief look at a small amount of traffic, localhost queries are
> basically all handled inside the stub, so it is de facto as you
> describe.

Just as an FYI data point:  On April 12th (a DITL day) B-root received
just shy of a million packets with ^localhost$ as the query name, which
amounted to .018% of the total traffic.
-- 
Wes Hardaker
USC/ISI


From nobody Wed Sep 13 11:59:17 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2882313207A; Wed, 13 Sep 2017 11:59:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150532915613.30493.15774734086217561468@ietfa.amsl.com>
Date: Wed, 13 Sep 2017 11:59:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1Nf9xL0DuJaQthyWLtWoqXqF2qg>
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 18:59:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

        Title           : Security Considerations for RFC5011 Publishers
        Authors         : Wes Hardaker
                          Warren Kumari
	Filename        : draft-ietf-dnsop-rfc5011-security-considerations-04.txt
	Pages           : 14
	Date            : 2017-09-13

Abstract:
   This document extends the RFC5011 rollover strategy with timing
   advice that must be followed in order to maintain security.
   Specifically, this document describes the math behind the minimum
   time-length that a DNS zone publisher must wait before signing
   exclusively with recently added DNSKEYs.  It contains much math and
   complicated equations, but the summary is that the key rollover /
   revocation time is much longer than intuition would suggest.  If you
   are not both publishing a DNSSEC trust anchor, and using RFC5011 to
   update that trust anchor, you probably don't need to read this
   document.

   This document also describes the minimum time-length that a DNS zone
   publisher must wait after publishing a revoked DNSKEY before assuming
   that all active RFC5011 resolvers should have seen the revocation-
   marked key and removed it from their list of trust anchors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc5011-security-considerations/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnsop-rfc5011-security-considerations-04
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc5011-security-considerations-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-rfc5011-security-considerations-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 13 16:43:30 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D29132D8C for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 16:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 8-xjmckqe1Oh for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 16:43:26 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50376132331 for <dnsop@ietf.org>; Wed, 13 Sep 2017 16:43:26 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id z143so4162133qkb.3 for <dnsop@ietf.org>; Wed, 13 Sep 2017 16:43:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=T1vLNLFEyl0XTU25Mbso6orCYBBciVY4EyZNeCnC+/c=; b=jUN0sgnDA5AGVfcZbtk9zzLdC3oI1stSsk7v49SeW4h64wuoRTNxR4DTHBukAci7gG rM5OMw/OGiCYozow5vWbFfUId1xfxKke6drHI1Wju7nD0JoUxLUIlNEqiVimnAZQmPu/ l531MUftrEP1oYJKnJL2FlAiye1WTyXji9QARIg3qrielUXS68gWs48+hCMW7HSu9NGO F09joExTW2UYFZKUxIZ1krLSrngYVOVDKyP92tPX5qaa/NQnv2hMGfmmreCIzPAfddaW wzCicaqVxTUogTiRphyZcqn2td2r+RxXphTxR9u3GDNo6jJcQJRSF4ZGzG3W/1OMY3to zOgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=T1vLNLFEyl0XTU25Mbso6orCYBBciVY4EyZNeCnC+/c=; b=m+zyjtPlwnncRvk8H/BfVVFspJE68xNxlBbqjUI2t4/z3oCJWt9EBJJMsH6gjMxrSz hQxDre1q7n9JynReazdnM6gBhs9o5U76wedLlhx7YTlZmKatNvnn7r3bFQT9NSEY4tfW RQCJntFhjHSDCqTFeTK/VSiGjDFVXuevJPMbfiEHsx3kjebf+kqaTzot6JJrk5ppTImU dY5T0zIPtt41Lg5stH+dd9M6miSx22wKxuOwfaAiKOAOJ4bE/YgmVmoWmLMSprLoYxu1 r3b+61uj03SbHu3N6hwJYLImTcUdQzGP/Ym8EmR+syICzPL+x/NeiqjrV//7MM6Y1h4O YztA==
X-Gm-Message-State: AHPjjUhN81IpBv84QSB6r6xJMU85VUXd6tkkHo42Iw28pxVY0yT17iuZ zqRtnawENBTuok+k
X-Google-Smtp-Source: AOwi7QAJ8CqIfs9e7rc9nAkIleSe4GXrqRt1AjovTrb4Y9cY9AR1C8jhNUVeJKawakbRkGEbUu+ZBg==
X-Received: by 10.55.167.197 with SMTP id q188mr294074qke.234.1505346205466; Wed, 13 Sep 2017 16:43:25 -0700 (PDT)
Received: from cavall.ether.lede.home (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id t123sm9870942qkh.39.2017.09.13.16.43.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Sep 2017 16:43:24 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <82F11EFD-0FB8-4E92-BF70-F0A1A1A00D07@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7ECD8E58-0CE8-43AF-92AD-B1AB78646B31"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 13 Sep 2017 19:43:23 -0400
In-Reply-To: <CAAiTEH9QwgC-aSPf2KZPOcQtZVmTRZek5OcbXTt-N+BOcCM=Zg@mail.gmail.com>
Cc: Mark Andrews <marka@isc.org>, dnsop WG <dnsop@ietf.org>
To: Matthew Pounsett <matt@conundrum.com>
References: <20170913021529.2540.qmail@ary.lan> <26E56255-6169-4626-95E8-A9D6A2D5EB39@fugue.com> <20170913030645.946E8855120E@rock.dv.isc.org> <25E28EFD-DF13-42F1-A872-400CC1CFBBF9@fugue.com> <CAAiTEH9QwgC-aSPf2KZPOcQtZVmTRZek5OcbXTt-N+BOcCM=Zg@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5SzFXxZYedUa6ohoIff0Iv09pe8>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 23:43:28 -0000

--Apple-Mail=_7ECD8E58-0CE8-43AF-92AD-B1AB78646B31
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 13, 2017, at 12:46 PM, Matthew Pounsett <matt@conundrum.com> =
wrote:
> I thought the goal was to ensure that localhost names map to loopback. =
 =20

No.  If that were the goal, we might well be proposing using DNS to =
provide that information.   The goal is to make localhost less of an =
attack surface.   At least that's _my_ goal!   :)


--Apple-Mail=_7ECD8E58-0CE8-43AF-92AD-B1AB78646B31
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 13, 2017, at 12:46 PM, Matthew Pounsett &lt;<a =
href=3D"mailto:matt@conundrum.com" class=3D"">matt@conundrum.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">I thought the goal was to ensure =
that localhost names map to loopback. =
&nbsp;&nbsp;</span></div></blockquote></div><br class=3D""><div =
class=3D"">No. &nbsp;If that were the goal, we might well be proposing =
using DNS to provide that information. &nbsp; The goal is to make =
localhost less of an attack surface. &nbsp; At least that's _my_ goal! =
&nbsp; :)</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_7ECD8E58-0CE8-43AF-92AD-B1AB78646B31--


From nobody Wed Sep 13 16:45:38 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 494C01320DC for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 16:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 T1W-oPQodB3T for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 16:45:35 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACC42126B7E for <dnsop@ietf.org>; Wed, 13 Sep 2017 16:45:35 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id z143so4169168qkb.3 for <dnsop@ietf.org>; Wed, 13 Sep 2017 16:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=WQ5MviNozFunyfMzXwFDl9txSxaL9ceU4FqH1uYV3BA=; b=IwBPC7oQJvqLEZDKpA4pnR8TDol0oYMko+AZSIU0TBibYBYeMHMLU6qPmIzabon6xN B+CLKJf0ln4eeRiWheSzWhCSrHRmRgdr5xA6LK0lS7HdlPtS8EcH8bGTOoOrdSTYQre2 6N3IYEjfnh6y/nvFui53KFL7ZL1N5yKlIMdurUJPwGjOeBHoXXqD0DUL2oCklcTj8H+y E4VK0SKKSBVdfDodWyMcn5Q8fv9NCpCgcDaCkI0RtK9UE8FcNaeJ3oHFfL+1HV7EJT3v LzIGOXHUoHQQFEmeFtU5yn32ICB+lZuxoTx8Bz5kfVgKhRAsWsFnmkR33xFif7B7219L SDrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=WQ5MviNozFunyfMzXwFDl9txSxaL9ceU4FqH1uYV3BA=; b=bB4VRMvXMMCSt7tvDLe9TRgp77oypQo2ExlLTi7E7oYoQEyeE8p9DxTSvbCaP7iXir ugckkZrBh2jLNwpd1yJSFWOtLXImakvjspbiGcAcK354Are8HOF0BCVeAzl5qMXAAiSy hPTWhCTXDaQ8FaZY8YrLtGR7UDPSPs+sonGz/+ebI7ix1pBrYCD2T1F1HnY+OovAI2DT c4DSoBHht+wwsZPRuaZkrBywo3JaE6kNGn4a02XF4+luJvrL/0EnxzV1YTyCHtdC+eoj 3qVa24//qmZKPRpPm5kjrFGOtlTlrIvwPOF/NHVxYZhp1Ogi6fZz9Dkvev9ohCPxMRta ndOQ==
X-Gm-Message-State: AHPjjUh69/V5SqkGCd95O5nQZm9QXwR2SROmoKRkVNXO7M0JXwXpWRi9 xjnH91sGRuL1QQRaGO7AVA==
X-Google-Smtp-Source: AOwi7QD6jpErB7AXV9VQYkYiBOP3a/55fzGcJQI1u9koPze9qdNj4y7AiCcCYnpAtbGtFnXnj/pkpg==
X-Received: by 10.55.36.3 with SMTP id w3mr305142qkg.284.1505346334468; Wed, 13 Sep 2017 16:45:34 -0700 (PDT)
Received: from cavall.ether.lede.home (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id w46sm4716596qta.84.2017.09.13.16.45.33 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Sep 2017 16:45:33 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5539AE07-3C44-46A7-8E17-7AF6F5792608"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 13 Sep 2017 19:45:32 -0400
References: <20170913171915.1194.qmail@ary.lan>
To: dnsop WG <dnsop@ietf.org>
In-Reply-To: <20170913171915.1194.qmail@ary.lan>
Message-Id: <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TBiaaTxSNBVQOT0pTJRh8j8oD6E>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 23:45:37 -0000

--Apple-Mail=_5539AE07-3C44-46A7-8E17-7AF6F5792608
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 13, 2017, at 1:19 PM, John Levine <johnl@taugh.com> wrote:
> I concur with Mark that while localhost.<foo> is a problem,
> <foo>.localhost is not.  I've occasionally used that hack to pass
> traffice to various servers running on 127/8 addresses other than
> 127.0.0.1.

So we should expose end-users to attack because it's "occasionally" =
convenient for you to do this hack?


--Apple-Mail=_5539AE07-3C44-46A7-8E17-7AF6F5792608
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Sep 13, 2017, at 1:19 PM, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">I concur with Mark =
that while localhost.&lt;foo&gt; is a problem,</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">&lt;foo&gt;.localhost is not. &nbsp;I've =
occasionally used that hack to pass</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">traffice to various =
servers running on 127/8 addresses other than</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">127.0.0.1.</span></div></blockquote></div><br =
class=3D""><div class=3D"">So we should expose end-users to attack =
because it's "occasionally" convenient for you to do this =
hack?</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_5539AE07-3C44-46A7-8E17-7AF6F5792608--


From nobody Wed Sep 13 17:54:58 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 749A6132F6C for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 17:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 1bjPcHFYud6B for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 17:54:54 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB9AD132F69 for <dnsop@ietf.org>; Wed, 13 Sep 2017 17:54:54 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 0D71A34C0DD; Thu, 14 Sep 2017 00:54:50 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id E6A0516007A; Thu, 14 Sep 2017 00:54:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C98DD160079; Thu, 14 Sep 2017 00:54:49 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id A-Yqt0gux9gD; Thu, 14 Sep 2017 00:54:49 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 6415716006C; Thu, 14 Sep 2017 00:54:49 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id DA4C1859D924; Thu, 14 Sep 2017 10:54:46 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: dnsop WG <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <20170913171915.1194.qmail@ary.lan> <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com>
In-reply-to: Your message of "Wed, 13 Sep 2017 19:45:32 -0400." <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com>
Date: Thu, 14 Sep 2017 10:54:46 +1000
Message-Id: <20170914005446.DA4C1859D924@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AglYqwSmPyPLmKVaAkDYhzyYueE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 00:54:56 -0000

In message <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com>, Ted Lemon writes:
> 
> On Sep 13, 2017, at 1:19 PM, John Levine <johnl@taugh.com> wrote:
> > I concur with Mark that while localhost.<foo> is a problem,
> > <foo>.localhost is not.  I've occasionally used that hack to pass
> > traffice to various servers running on 127/8 addresses other than
> > 127.0.0.1.
> 
> So we should expose end-users to attack because it's "occasionally" =
> convenient for you to do this hack?

The biggest problem is that HTTP says that hostnames in URLs may
be relative.  Close that grand canyon sized security hole.  There
is zero need for relative names in URL's in html documents, email
etc.  There is some need for them in address bars but that is UI.
What goes over the wire should be treated as absolute, always.

Treat "localhost" as always being absolute.  No searching if that
is the entered hostname.  Yes, this will break somethings that
depend on searching to find localhost.*.  It is the one hangover
from the flat global namespace we still have.

Have public DNS return unsigned NODATA for localhost (qtype != SOA,
NS, DS) and signed NODATA for localhost DS.

getaddrinfo() et al. is still free to hardcode localhost -> (::1,
127.0.0.1) if the implementation wants to.  Make it a requirement
for *browsers* (includes curl, fetch, lynx etc.) to do this if you
want.

Recommend that recursive servers have a "localhost." zone with ::1
and 127.0.0.1 for "localhost." built in by default.

You don't need to sabatage the DNS.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Sep 13 18:05:04 2017
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518B9132F73 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 18:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 Xyk0813yP_CL for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 18:05:00 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D153132F69 for <dnsop@ietf.org>; Wed, 13 Sep 2017 18:05:00 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id q76so2758119pfq.2 for <dnsop@ietf.org>; Wed, 13 Sep 2017 18:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X8yVV5c+K0MWZMEI5crtTvnbpV8tE87LE8morYasfcg=; b=pFqeQYkOhTqnFZGMZy6dX4WAfxD6b0EkhbtOBnap0erYKQiNqg7cz990xU+OU68p5d AKNz+Vs2BPi6wkz/MtufaiITsV0oTIT12ny9rirWwm9p2jc7oJAaSZUlBnocV777LAnT ad8Esbb4UBEda/RZ24thg/X+xBYCAE/46Kv0bP6VkF9nENvxJJ18XJTv24rWc1Z/MXyt WW8us/k/p5d6qUbLSi+ithXxRsaz3wQcJePvtWHo1f7FmpwRpYCVsBs3kI3BMWnxkwo2 ReSsr6DTbg+7ylILKDgac42sdx7h/6OnmV6hcjIZZxjJ/yFwR8ICGSqcR5WV4jDdQhvw m63w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X8yVV5c+K0MWZMEI5crtTvnbpV8tE87LE8morYasfcg=; b=s7uNTxpqDuy9No+74Td5m7ccqNOEeDUUgi6TqQys9BFK59JTWl5QgAM1p0uNw09HYK QGT39zEy3xmtI/0zrVL8hnBB03j0xUEHDbos8h7/8+CEMd7CciAhah+TJMGagO4zXSAp 5mtiK5Zt1YHD4xGkUaYTMNeD9/0l+i875LBPXW4es51SlDT2MHmzIvomz2n630N2Nm3Y PPNFepjnVD7/2ls31uJ8n8h6E8I0H+YRKobJ6VvtYoZmNqF3vunegGBnxhpYPE6LCSyu Myhr4EahXXFBFRd6U2udsTPSHxIoKThYhF2p85XZu16MG4yIRB3972bDThgY4+hoOCpH ivtg==
X-Gm-Message-State: AHPjjUgFAdKB/r/JsQ4XIXJeez/HTfnbie1Fjxk1co5hUwnCXZUw9xfe dyc1ApONpfA0+K+KbOVGWQn01lXpb5IzLvdboNTKkg==
X-Google-Smtp-Source: AOwi7QDemdmUa9XfOQ4QPOM8raTpe2yaFAgR1LiCKJSQeyk2Wk3Uv+UCYKIFLbzCkMHRQ+d9b0QHUvNGi990ScaLjvw=
X-Received: by 10.101.67.137 with SMTP id m9mr476182pgp.63.1505351099758; Wed, 13 Sep 2017 18:04:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.152.98 with HTTP; Wed, 13 Sep 2017 18:04:58 -0700 (PDT)
Received: by 10.100.152.98 with HTTP; Wed, 13 Sep 2017 18:04:58 -0700 (PDT)
In-Reply-To: <20170914005446.DA4C1859D924@rock.dv.isc.org>
References: <20170913171915.1194.qmail@ary.lan> <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com> <20170914005446.DA4C1859D924@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 13 Sep 2017 21:04:58 -0400
Message-ID: <CAPt1N1kAGrm6DXJty8xfm1P8ZEutD+7C1o=CmdnFEdSMrXmXOw@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="089e08200b64904c6905591bdd1f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/n5QOXQjYAY3v7agslubLPJepe9g>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 01:05:02 -0000

--089e08200b64904c6905591bdd1f
Content-Type: text/plain; charset="UTF-8"

You've made your position clear, thanks.

On Sep 13, 2017 20:54, "Mark Andrews" <marka@isc.org> wrote:

>
> In message <714677EA-E3C8-4145-825C-5BA8EABD018C@fugue.com>, Ted Lemon
> writes:
> >
> > On Sep 13, 2017, at 1:19 PM, John Levine <johnl@taugh.com> wrote:
> > > I concur with Mark that while localhost.<foo> is a problem,
> > > <foo>.localhost is not.  I've occasionally used that hack to pass
> > > traffice to various servers running on 127/8 addresses other than
> > > 127.0.0.1.
> >
> > So we should expose end-users to attack because it's "occasionally" =
> > convenient for you to do this hack?
>
> The biggest problem is that HTTP says that hostnames in URLs may
> be relative.  Close that grand canyon sized security hole.  There
> is zero need for relative names in URL's in html documents, email
> etc.  There is some need for them in address bars but that is UI.
> What goes over the wire should be treated as absolute, always.
>
> Treat "localhost" as always being absolute.  No searching if that
> is the entered hostname.  Yes, this will break somethings that
> depend on searching to find localhost.*.  It is the one hangover
> from the flat global namespace we still have.
>
> Have public DNS return unsigned NODATA for localhost (qtype != SOA,
> NS, DS) and signed NODATA for localhost DS.
>
> getaddrinfo() et al. is still free to hardcode localhost -> (::1,
> 127.0.0.1) if the implementation wants to.  Make it a requirement
> for *browsers* (includes curl, fetch, lynx etc.) to do this if you
> want.
>
> Recommend that recursive servers have a "localhost." zone with ::1
> and 127.0.0.1 for "localhost." built in by default.
>
> You don't need to sabatage the DNS.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

--089e08200b64904c6905591bdd1f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">You&#39;ve made your position clear, thanks.=C2=A0</div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sep 13, 2017 20=
:54, &quot;Mark Andrews&quot; &lt;<a href=3D"mailto:marka@isc.org">marka@is=
c.org</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><br>
In message &lt;<a href=3D"mailto:714677EA-E3C8-4145-825C-5BA8EABD018C@fugue=
.com">714677EA-E3C8-4145-825C-<wbr>5BA8EABD018C@fugue.com</a>&gt;, Ted Lemo=
n writes:<br>
&gt;<br>
&gt; On Sep 13, 2017, at 1:19 PM, John Levine &lt;<a href=3D"mailto:johnl@t=
augh.com">johnl@taugh.com</a>&gt; wrote:<br>
&gt; &gt; I concur with Mark that while localhost.&lt;foo&gt; is a problem,=
<br>
&gt; &gt; &lt;foo&gt;.localhost is not.=C2=A0 I&#39;ve occasionally used th=
at hack to pass<br>
&gt; &gt; traffice to various servers running on 127/8 addresses other than=
<br>
&gt; &gt; 127.0.0.1.<br>
&gt;<br>
&gt; So we should expose end-users to attack because it&#39;s &quot;occasio=
nally&quot; =3D<br>
&gt; convenient for you to do this hack?<br>
<br>
The biggest problem is that HTTP says that hostnames in URLs may<br>
be relative.=C2=A0 Close that grand canyon sized security hole.=C2=A0 There=
<br>
is zero need for relative names in URL&#39;s in html documents, email<br>
etc.=C2=A0 There is some need for them in address bars but that is UI.<br>
What goes over the wire should be treated as absolute, always.<br>
<br>
Treat &quot;localhost&quot; as always being absolute.=C2=A0 No searching if=
 that<br>
is the entered hostname.=C2=A0 Yes, this will break somethings that<br>
depend on searching to find localhost.*.=C2=A0 It is the one hangover<br>
from the flat global namespace we still have.<br>
<br>
Have public DNS return unsigned NODATA for localhost (qtype !=3D SOA,<br>
NS, DS) and signed NODATA for localhost DS.<br>
<br>
getaddrinfo() et al. is still free to hardcode localhost -&gt; (::1,<br>
127.0.0.1) if the implementation wants to.=C2=A0 Make it a requirement<br>
for *browsers* (includes curl, fetch, lynx etc.) to do this if you<br>
want.<br>
<br>
Recommend that recursive servers have a &quot;localhost.&quot; zone with ::=
1<br>
and 127.0.0.1 for &quot;localhost.&quot; built in by default.<br>
<br>
You don&#39;t need to sabatage the DNS.<br>
<br>
Mark<br>
--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: +61 2 9871 4742=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</blockquote></div></div>

--089e08200b64904c6905591bdd1f--


From nobody Wed Sep 13 20:48:02 2017
Return-Path: <abbypan@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27EE51330A1 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 20:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 YL354POsEn6v for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 20:47:58 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66B7132811 for <dnsop@ietf.org>; Wed, 13 Sep 2017 20:47:57 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id 189so2600162wmh.1 for <dnsop@ietf.org>; Wed, 13 Sep 2017 20:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AqEhIvAMOQIkDMiYes/g0bbzq7Tp4Cr27wYDDOL4JNA=; b=Z1rgOzpelUU6hr9KSfyvltbn5B5d2bBRCF++oaCgiySn1v6jDrahd+nJvBZpaXl/oW VLufPFMxqNSz6pWX10IQMBo8qrQsbFYFEB31DFrrreCMniiYQJIKEpEyEp+kEHEBv9i2 O4Qx1WrOIDxtXdNluk5HT5h0DzoSFjWCE8F88N2fPU1Bg4NH8EoVUbEQqcXyJNLOFUat Uy+edwRWv1Nt0HtDmBW+UVm4djKNfsCK73X3BSCld8ikaFMI1Iq8EwDVmWvv44AIrSnr FA5uARA+N4rQvMbRbgo71F/Gn0c9+6IIb9SwMv9AbIntLuoaP7mGvMqGcXFCq42D+GSR ZXjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AqEhIvAMOQIkDMiYes/g0bbzq7Tp4Cr27wYDDOL4JNA=; b=exLXAcgfbB9H60l0Dkud/FTiw1oCfqcQWAXiFg96RiT/eWtD0Lu330FWBnRQOz9V3Y AA8GGsbbCHek9gnVQOhBagDtdFQ9fj0HFdIH7mxnb0ah1Qcv0CQSghjZ13KUY52jxWRQ m1eW3EP8McIAAadK4uK70N9PUspoyq9bTCxR8WL1hdO+r5CJyNKJEOYmHP+roccYsEgQ Ef14pFJ3Cl4/E7NIH0UYFhsr44DSKMdRC4HzeRIUSMpcqU7uLMN+LClSMhjCPXuo4a8X dSWJv+nndNS03CKYyAPSw/dWHSMmWfUyV3c2q9opjWNM1MQoFWrdoVkhXqHVmUOmxCh9 JFOA==
X-Gm-Message-State: AHPjjUhaUzi6hTC+5u+nmD/nxNfodH7gOQY6BDddY6zx2oDVq1Ox80JM hUc/2Fo3ar+ZO88/Z5eUAqefGrAc1b0B2cK8jQw=
X-Google-Smtp-Source: ADKCNb6Ssl+rHgmSV78qC1ARbkfaUWESimS9qdh4jidNbvCBXwZLVxuyCfjOsH7MVCKmaGrlO/2P79gnD2PR2Tmb7mM=
X-Received: by 10.80.144.163 with SMTP id c32mr17455595eda.30.1505360876452; Wed, 13 Sep 2017 20:47:56 -0700 (PDT)
MIME-Version: 1.0
References: <20170911013510.17202.qmail@ary.lan> <yblr2vcxzjn.fsf@w7.hardakers.net> <alpine.DEB.2.11.1709121124250.2628@grey.csi.cam.ac.uk> <59B7F771.5020607@redbarn.org> <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.11.1709121646180.2676@grey.csi.cam.ac.uk>
From: Lanlan Pan <abbypan@gmail.com>
Date: Thu, 14 Sep 2017 03:47:45 +0000
Message-ID: <CANLjSvU8YBoC7k0KiYwhS4mi7E80-131_mrBytmNhzFVezD1TA@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114ffae84cc02505591e249f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6t0Ba9RpBXe5ZVRpu_Fu9MJGUCw>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 03:48:00 -0000

--001a114ffae84cc02505591e249f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

no only localhost.example.com : http://seclists.org/bugtraq/2008/Jan/270
if xxx.example.com is NXDOMAIN , there is similar risk cause by the
"nxdomain redirect" recursive dns (they return a hijack A RR ).
CA SSO (siteminder)  may be a solution.

localhost.  seems a new special-use TLD, like arpa. , local.

Tony Finch <dot@dotat.at>=E4=BA=8E2017=E5=B9=B49=E6=9C=8812=E6=97=A5=E5=91=
=A8=E4=BA=8C =E4=B8=8B=E5=8D=8811:54=E5=86=99=E9=81=93=EF=BC=9A

> Paul Vixie <paul@redbarn.org> wrote:
> >
> > while i've generally included a localhost.$ORIGIN A RR in zones that
> appear in
> > my stub resolver search lists, in order that "localhost" be found,
>
> I agree with the rest of your message but I want to highlight this bit
> because it is directly related to the main reason this draft exists.
>
> Your localhost records (like the ones I deleted from cam.ac.uk last week)
> are troublesome for the web browser same origin security policy: they can
> lead to vulnerabilites when your websites are accessed from multi-user
> machines and in other more obscure circumstances - for details, see
> http://seclists.org/bugtraq/2008/Jan/270
>
> Tony.
> --
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h
> punycode
> Tyne, Dogger: Westerly backing southeastrly 4 or 5, occasionally 6 at
> first,
> then becoming cyclonic, mainly northwesterly later, 6 to gale 8,
> occasionally
> severe gale 9 later in south. Moderate or rough, occasionally very rough
> later
> in south. Rain. Good occasionally poor.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
--=20
=E8=87=B4=E7=A4=BC  Best Regards

=E6=BD=98=E8=93=9D=E5=85=B0  Pan Lanlan

--001a114ffae84cc02505591e249f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>no only <a href=3D"http://localhost.example.com" targ=
et=3D"_blank">localhost.example.com</a>



: <a href=3D"http://seclists.org/bugtraq/2008/Jan/270" rel=3D"noreferrer" t=
arget=3D"_blank">http://seclists.org/bugtraq/2008/Jan/270</a>

<br>if <a href=3D"http://xxx.example.com" target=3D"_blank">xxx.example.com=
</a> is NXDOMAIN

, there is similar risk cause by the &quot;nxdomain redirect&quot; recursiv=
e dns (they return a hijack A RR ).=C2=A0 <br></div>CA SSO (siteminder)=C2=
=A0 may be a solution.

<div><div><div><br></div><div>localhost.=C2=A0 seems a new special-use TLD,=
 like arpa. , local. <br></div><div><div><div><div><div><div></div></div></=
div></div></div></div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">Tony Finch &lt;<a href=3D"mailto:dot@dotat.at">dot@dotat.at</a>&gt=
;=E4=BA=8E2017=E5=B9=B49=E6=9C=8812=E6=97=A5=E5=91=A8=E4=BA=8C =E4=B8=8B=E5=
=8D=8811:54=E5=86=99=E9=81=93=EF=BC=9A<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Paul Vixie &lt;<a href=3D"mailto:paul@redbarn.org" target=3D"_blank">pa=
ul@redbarn.org</a>&gt; wrote:<br>
&gt;<br>
&gt; while i&#39;ve generally included a localhost.$ORIGIN A RR in zones th=
at appear in<br>
&gt; my stub resolver search lists, in order that &quot;localhost&quot; be =
found,<br>
<br>
I agree with the rest of your message but I want to highlight this bit<br>
because it is directly related to the main reason this draft exists.<br>
<br>
Your localhost records (like the ones I deleted from <a href=3D"http://cam.=
ac.uk" rel=3D"noreferrer" target=3D"_blank">cam.ac.uk</a> last week)<br>
are troublesome for the web browser same origin security policy: they can<b=
r>
lead to vulnerabilites when your websites are accessed from multi-user<br>
machines and in other more obscure circumstances - for details, see<br>
<a href=3D"http://seclists.org/bugtraq/2008/Jan/270" rel=3D"noreferrer" tar=
get=3D"_blank">http://seclists.org/bugtraq/2008/Jan/270</a><br>
<br>
Tony.<br>
--<br>
f.anthony.n.finch=C2=A0 &lt;<a href=3D"mailto:dot@dotat.at" target=3D"_blan=
k">dot@dotat.at</a>&gt;=C2=A0 <a href=3D"http://dotat.at/" rel=3D"noreferre=
r" target=3D"_blank">http://dotat.at/</a>=C2=A0 -=C2=A0 I xn--zr8h punycode=
<br>
Tyne, Dogger: Westerly backing southeastrly 4 or 5, occasionally 6 at first=
,<br>
then becoming cyclonic, mainly northwesterly later, 6 to gale 8, occasional=
ly<br>
severe gale 9 later in south. Moderate or rough, occasionally very rough la=
ter<br>
in south. Rain. Good occasionally poor.<br>
<br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=E8=87=B4=E7=
=A4=BC=C2=A0 Best Regards<br><br>=E6=BD=98=E8=93=9D=E5=85=B0=C2=A0 Pan Lanl=
an<br></div></div>

--001a114ffae84cc02505591e249f--


From nobody Wed Sep 13 21:18:48 2017
Return-Path: <abbypan@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72A51330A6 for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 21:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5PpIqh1C9-TO for <dnsop@ietfa.amsl.com>; Wed, 13 Sep 2017 21:18:45 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38BB4132D89 for <dnsop@ietf.org>; Wed, 13 Sep 2017 21:18:45 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id g206so4351355wme.0 for <dnsop@ietf.org>; Wed, 13 Sep 2017 21:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fqFQHve39ctl5E9IUVYSWYnpHQQVqAqM9oUvYrfM92Q=; b=VDuKhywTQIuge2aD45EZeI0jeRE/KtOMt5SIFQOFvEWsA07+L8CoOROvcAIws4ArQK WNBUJ/aIc3jm6VcZLNPWN7/pE/4nJhWCdr/4FL7pWStRLyTwF/RwoI1e9VPKW2aj/XVx /cIrISIy50iifwhXxkrK4daooSJSD1xd69r9w8rp5OzwWZOcyl1P9LWIL8TUm/Y0146y dbZWGNTc+gPWvCDN1AJh49VTzWbxrFozkorTz6PgsdhdxH7pYH6WaDf0OvUUOT38gm7Y 0YfGypT424kLnrl/to2FuyCiKDoLeAmPAIIXCkwAgaSvo2dmpkmdfuIbnIF5YxBCkLYx F0pQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fqFQHve39ctl5E9IUVYSWYnpHQQVqAqM9oUvYrfM92Q=; b=VTDt+4xR2QtIyBI04B29XOwlnJMPr7CMvDrwVwZS551zvnrkjQj97L3QrqZkzi6YKg vlgQMmIN1wKHD4KszXJdkBotolsDxYytQ6+hV58m0dou1ES2WFtxteqdmrgfoPdKv4JI XDZQk34duN/HbcnCt6UOfDp5esxQMRWifP+WHwWb3layU47706Gi1FigyvIKVk/4bKpt LoWZ54St0/30LMb0WxcJgVdKzWK2Wb4gfJ0T0jBh6OC6FQadv9Ezy2GVH90k83oIXn4+ GuN6T31iyhIIMp36FeiCQAd4har3UO+28sCt9GgYEpzqdROfaZzwZJJKyZaFpMyVTGm/ kdbw==
X-Gm-Message-State: AHPjjUg64YV31uRfPz4DfIZ6jq71BsrKhpDAaE94nX2XZkjoLcbZF9Ni D74YfqxrjcNsZtp/gkh19Oca5TwKTIAoOw92A1K4TA==
X-Google-Smtp-Source: ADKCNb46p/8FbY/Q8l4Ks1L3+kTnj5RUPboRrVbJJf8vUOSbJOL9AJ4lhSboNb4YRp/kxvhS0THG78QzYgjYyIoGgpI=
X-Received: by 10.80.172.60 with SMTP id v57mr16378915edc.118.1505362723769; Wed, 13 Sep 2017 21:18:43 -0700 (PDT)
MIME-Version: 1.0
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CANLjSvVpFkZiTv1k31DdOCvXByU=OkRwiryQ5O2iA9Wmgksuhw@mail.gmail.com> <20170912150659.vub6yf6e25nup775@nic.fr> <59B7F9D6.50900@redbarn.org>
In-Reply-To: <59B7F9D6.50900@redbarn.org>
From: Lanlan Pan <abbypan@gmail.com>
Date: Thu, 14 Sep 2017 04:18:33 +0000
Message-ID: <CANLjSvUG0gObmUDjh-3gmYodCHGzoefeY9rOXVb9g6VCbA7png@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Davey Song <songlinjian@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045c38ec68924605591e925d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/7hC2nuXOCE-RFUs_OXRqQ5GflD8>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 04:18:47 -0000

--f403045c38ec68924605591e925d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Paul Vixie <paul@redbarn.org>=E4=BA=8E2017=E5=B9=B49=E6=9C=8812=E6=97=A5=E5=
=91=A8=E4=BA=8C =E4=B8=8B=E5=8D=8811:14=E5=86=99=E9=81=93=EF=BC=9A

>
>
> Stephane Bortzmeyer wrote:
> > On Tue, Sep 12, 2017 at 09:50:37AM +0000,
> >   Lanlan Pan<abbypan@gmail.com>  wrote
> >   a message of 210 lines which said:
> >
> >> ATR make Authoritative Servers send normal big response packet
> >> before they try to send TC response for large RRsets ?
> >
> > Yes, section 3. "it is suggested a timer to delay the second truncated
> > response to around 10 millisecond which can be configured by local
> > operation". (In the spirit of RFC 6555.)
>

Thanks Stephane,  got it, :-)


> noting, 10ms isn't enough. packet reordering due to multipath load
> balancing has been observed as high as 60ms due to "buffer bloat".
>

TC may be a safer choice for recursive nowadays ?


> --
> P Vixie
>
> --
=E8=87=B4=E7=A4=BC  Best Regards

=E6=BD=98=E8=93=9D=E5=85=B0  Pan Lanlan

--f403045c38ec68924605591e925d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">P=
aul Vixie &lt;<a href=3D"mailto:paul@redbarn.org">paul@redbarn.org</a>&gt;=
=E4=BA=8E2017=E5=B9=B49=E6=9C=8812=E6=97=A5=E5=91=A8=E4=BA=8C =E4=B8=8B=E5=
=8D=8811:14=E5=86=99=E9=81=93=EF=BC=9A<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><br>
<br>
Stephane Bortzmeyer wrote:<br>
&gt; On Tue, Sep 12, 2017 at 09:50:37AM +0000,<br>
&gt;=C2=A0 =C2=A0Lanlan Pan&lt;<a href=3D"mailto:abbypan@gmail.com" target=
=3D"_blank">abbypan@gmail.com</a>&gt;=C2=A0 wrote<br>
&gt;=C2=A0 =C2=A0a message of 210 lines which said:<br>
&gt;<br>
&gt;&gt; ATR make Authoritative Servers send normal big response packet<br>
&gt;&gt; before they try to send TC response for large RRsets ?<br>
&gt;<br>
&gt; Yes, section 3. &quot;it is suggested a timer to delay the second trun=
cated<br>
&gt; response to around 10 millisecond which can be configured by local<br>
&gt; operation&quot;. (In the spirit of RFC 6555.)<br></blockquote><div><br=
>Thanks Stephane,=C2=A0 got it, :-)<br><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
<br>
noting, 10ms isn&#39;t enough. packet reordering due to multipath load<br>
balancing has been observed as high as 60ms due to &quot;buffer bloat&quot;=
.<br></blockquote><div><br>TC may be a safer choice for recursive nowadays =
? <br><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
P Vixie<br>
<br>
</blockquote></div></div></div><div dir=3D"ltr">-- <br></div><div class=3D"=
gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=E8=87=
=B4=E7=A4=BC=C2=A0 Best Regards<br><br>=E6=BD=98=E8=93=9D=E5=85=B0=C2=A0 Pa=
n Lanlan<br></div></div>

--f403045c38ec68924605591e925d--


From nobody Thu Sep 14 02:25:36 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0440C133188 for <dnsop@ietfa.amsl.com>; Thu, 14 Sep 2017 02:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 0_KvF5Fls9Pb for <dnsop@ietfa.amsl.com>; Thu, 14 Sep 2017 02:25:33 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68B2D1329C8 for <dnsop@ietf.org>; Thu, 14 Sep 2017 02:25:32 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 7C928281A49 for <dnsop@ietf.org>; Thu, 14 Sep 2017 11:25:30 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 77D85281A4D; Thu, 14 Sep 2017 11:25:30 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 714BE281A49 for <dnsop@ietf.org>; Thu, 14 Sep 2017 11:25:30 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 6ECCC642A7A6 for <dnsop@ietf.org>; Thu, 14 Sep 2017 11:25:30 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 690874076E; Thu, 14 Sep 2017 11:25:30 +0200 (CEST)
Date: Thu, 14 Sep 2017 11:25:30 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dnsop@ietf.org
Message-ID: <20170914092530.jiukd3jq54wcdehb@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000184, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.9.14.92117
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-NROEiqx7XnzLRuPjdWQZcf58Lk>
Subject: [DNSOP] [Humour] "dotted-decimal domain names"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 09:25:35 -0000

I just discovered this gem (last paragraph of the documentation):

http://cr.yp.to/djbdns/dnscache.html

"dnscache handles dotted-decimal domain names internally, giving
(e.g.) the domain name 192.48.96.2 an A record of 192.48.96.2."

And this prediction:

https://cr.yp.to/djbdns/namedroppers/20000220195445-21265-qmail@cr-yp-to

"Eventually, no matter what DNSEXT does, dotted-decimal domain names
will be a de facto standard."

Old and unmaintained software can bring funny surprises.


From nobody Thu Sep 14 05:03:03 2017
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8EC13301B for <dnsop@ietfa.amsl.com>; Thu, 14 Sep 2017 05:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 D94rZyPeMbpa for <dnsop@ietfa.amsl.com>; Thu, 14 Sep 2017 05:02:59 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E81E132F3F for <dnsop@ietf.org>; Thu, 14 Sep 2017 05:02:59 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id EABE46A407; Thu, 14 Sep 2017 14:02:57 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id A24756A3FA; Thu, 14 Sep 2017 14:02:54 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59ba6fee-034f-7f000001272a-7f0000018a6b-1 for <multiple-recipients>; Thu, 14 Sep 2017 14:02:54 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id 368016A324; Thu, 14 Sep 2017 14:02:54 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id 2ABF23C1993; Thu, 14 Sep 2017 14:02:54 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJi_T8KbB8Nd; Thu, 14 Sep 2017 14:02:54 +0200 (CEST)
Received: from [192.168.0.20] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 00B7E3C198D; Thu, 14 Sep 2017 14:02:53 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Thu, 14 Sep 2017 14:03:29 +0200
Message-ID: <E7C2107B-5552-4AC1-8576-949C1471D70B@powerdns.com>
In-Reply-To: <20170913163355.1038.qmail@ary.lan>
References: <20170913163355.1038.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.7r5412)
X-purgate-ID: 151428::1505390574-0000034F-3B0613B8/0/0
X-purgate-type: clean
X-purgate-size: 782
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/w0ZOOhYEh7MJ3d5FVEFoX9bsjiE>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 12:03:01 -0000

Hi John,

On 13 Sep 2017, at 18:33, John Levine wrote:

>> I would settle for SHOULD NOT. Can you elaborate on the debugging?
>
> There is something strange going on with my remote server, and I use
> localhost.mydomain so a little debugging server on my own computer
> can steal state and see whats going on.
>
> On the other hand, I could do this just as well:
>
> gazornplotz.mydomain IN A 127.0.0.1
>
> so never mind.  Still not sure I haven't missed something, though.

But now (with either name) you are exposing users of your server to the 
exact problems described in http://seclists.org/bugtraq/2008/Jan/270. 
Why not use /etc/hosts instead, so you only expose yourself?

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Sun Sep 17 20:19:09 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1110C1270AB; Sun, 17 Sep 2017 20:19:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.61.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150570474802.613.6489161595724212264@ietfa.amsl.com>
Date: Sun, 17 Sep 2017 20:19:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sBv0ut_ShT8n1RkLVSwZjNTI-hE>
Subject: [DNSOP] I-D Action: draft-yao-dnsop-accompanying-questions-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 03:19:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

        Title           : A DNS Query including A Main Question with Accompanying Questions
        Authors         : Jiankang Yao
                          Paul Vixie
                          Ning Kong
                          Xiaodong Li
	Filename        : draft-yao-dnsop-accompanying-questions-04.txt
	Pages           : 11
	Date            : 2017-09-17

Abstract:
   This document enables DNS initiators to send a main question
   accompanying with several related questions in a single DNS query,
   and enables DNS responders to put the answers into a single DNS
   response.  This extension enables a range of initiators to look up
   "X, or failing that, Y" in a better way than both current
   alternatives.  This mechanism can reduce the number of DNS round-
   trips per application work-unit.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-yao-dnsop-accompanying-questions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-yao-dnsop-accompanying-questions-04
https://datatracker.ietf.org/doc/html/draft-yao-dnsop-accompanying-questions-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-yao-dnsop-accompanying-questions-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep 18 19:48:33 2017
Return-Path: <rgibson@dyn.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C436F12895E for <dnsop@ietfa.amsl.com>; Mon, 18 Sep 2017 19:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dyn.com
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 ng3H1wkQEw7u for <dnsop@ietfa.amsl.com>; Mon, 18 Sep 2017 19:48:30 -0700 (PDT)
Received: from mail-io0-x247.google.com (mail-io0-x247.google.com [IPv6:2607:f8b0:4001:c06::247]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5620812426E for <dnsop@ietf.org>; Mon, 18 Sep 2017 19:48:30 -0700 (PDT)
Received: by mail-io0-x247.google.com with SMTP id k101so4906041iod.1 for <dnsop@ietf.org>; Mon, 18 Sep 2017 19:48:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dyn.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=XdDlqSzP+mhVreazXW/7rjHcZP35SuvgYuZRAtVLEQs=; b=Nzx4MNm3T2PtWFTi2Zf4LdGPaVhIEKFqDHGq6jmcUdlkcwuZwX6ilVqBbaXuGv/T4f Xi9k1zBBoBXwBn4MqOXxdCW3WanylPkgJIvOsN2LDkjL8LUEtHeXr2sO820bXF0ACxjz INYrdBw+xoH1VjjQAxOAyTiP98oZM3DOjjl8E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=XdDlqSzP+mhVreazXW/7rjHcZP35SuvgYuZRAtVLEQs=; b=WRiNIomPiQuMLr8apmBWzQx4/XhpUWoo6DKR7PyWrtAENW+mfRufJTgPiztG3xjeSD YOdHI/VVB6ZPRnSh09LUolSNt32HK6U59CaWXpIuaaZp4L49tS7p0aG5/IgX/zrzZ2LY vwkVmQfh90m6G9fZC36EXEzlQFIXqFE8k2trLTxcft3BUfkFMhtOQjiyQweuHG3GVLfv ir8ubWeGmw+lGXdN7TiAY4eQok0FKn2CK0y9GRkoQo1rihm+D2SpUgY0/n5NNev/4W8G VEpXKImYsEUcDNKIDvwWI5/caQedGP5/c0O5hEDWa/gRt3J4hGo7C2NK6Lszig9W4GoW OHJw==
X-Gm-Message-State: AHPjjUgbAMS+a7aFhkN0soFXtNOQ9EPqyQJNf/2d67qfWpOjQrOtvZBO flmRYGeRiUDFyShkME39bbFQEezNtMJln6bBoI1aTyloZzM=
X-Google-Smtp-Source: AOwi7QB7aMUAQcLLadMRWE02lxvZD4WO603K1dEcrt6AFHIy/znUVSQ0/u00tLlU/J0NYDDRKdyR9wjhPEJf8t/IHBQ=
X-Received: by 10.107.20.14 with SMTP id 14mr21671686iou.69.1505789302849; Mon, 18 Sep 2017 19:48:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.133.7 with HTTP; Mon, 18 Sep 2017 19:48:02 -0700 (PDT)
In-Reply-To: <150570474802.613.6489161595724212264@ietfa.amsl.com>
References: <150570474802.613.6489161595724212264@ietfa.amsl.com>
From: Richard Gibson <rgibson@dyn.com>
Date: Mon, 18 Sep 2017 22:48:02 -0400
Message-ID: <CAC94RYbqkTFcK_cN8o6wXsxq6htBkaRHoGrCDiZ8bWvXexMstQ@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114fcaa080dcaf055981e431"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YefZIsI7RL2m8ikWyyThdrCGYKg>
Subject: Re: [DNSOP] I-D Action: draft-yao-dnsop-accompanying-questions-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 02:48:33 -0000

--001a114fcaa080dcaf055981e431
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I have some questions about this draft.

How should responders populate the COUNT fields when one record answers
multiple accompanying questions? For example, assume example.com has an MX
record but no A or AAAA (the latter two thus being covered by an authority
section SOA):

QUESTION example.com. IN MX

AQ example.com. IN A

AQ example.com. IN AAAA

ANSWER example.com. 3600 IN MX 10 mail.example.net.

AUTHORITY example.com. 3600 IN SOA =E2=80=A6

ADDITIONAL . 0 CLASS4096 OPT ???


In a more general sense, how are responders to generate=E2=80=94and how are
initiators to interpret=E2=80=94responses in which it is not clear which qu=
estion
any given response record corresponds to?

Section 3 defines the prefix field of an accompanying question as "a domain
name with the form of a dot or a sequence of labels ending with a
pointer"... could you clarify that "the form of a dot" refers to the root
domain name (i.e., a single null label with wire format 0x00)?

In section 4, what is meant by "the responder assembles the prefix with the
main domain name"? Wire-format domain names are necessarily
fully-qualified, whether or not they end with compression pointers. Is the
operation to be interpreted as something like "if the prefix is the DNS
root domain, treat it as the QNAME"? If so, I think such special processing
is unnecessary, because it's already possible to reference the QNAME
directly with a compression pointer.

Why require accompanying question names to match or be subdomains of the
QNAME? It precludes potentially useful queries like QNAME=3Dwww.example.com=
.
accompanied by prefix=3Dstatic.example.com., and prohibiting them doesn't
prevent out-of-bailiwick queries anyway.

Section 5 references a "not been implemented, too many
accompanying-questions." response... what would that response look like?


On Sun, Sep 17, 2017 at 11:19 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations WG of the
> IETF.
>
>         Title           : A DNS Query including A Main Question with
> Accompanying Questions
>         Authors         : Jiankang Yao
>                           Paul Vixie
>                           Ning Kong
>                           Xiaodong Li
>         Filename        : draft-yao-dnsop-accompanying-questions-04.txt
>         Pages           : 11
>         Date            : 2017-09-17
>
> Abstract:
>    This document enables DNS initiators to send a main question
>    accompanying with several related questions in a single DNS query,
>    and enables DNS responders to put the answers into a single DNS
>    response.  This extension enables a range of initiators to look up
>    "X, or failing that, Y" in a better way than both current
>    alternatives.  This mechanism can reduce the number of DNS round-
>    trips per application work-unit.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-yao-dnsop-accompanying-questions/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-yao-dnsop-accompanying-questions-04
> https://datatracker.ietf.org/doc/html/draft-yao-dnsop-
> accompanying-questions-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-yao-dnsop-
> accompanying-questions-04
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--001a114fcaa080dcaf055981e431
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have some questions about this draft.<div><br></div><div=
>How should responders populate the COUNT fields when one record answers mu=
ltiple accompanying questions? For example, assume <a href=3D"http://exampl=
e.com">example.com</a> has an MX record but no A or AAAA (the latter two th=
us being covered by an authority section SOA):</div><div><blockquote style=
=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div>QUESTION <a href=
=3D"http://example.com">example.com</a>. IN MX</div></blockquote><blockquot=
e style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div>AQ <a href=
=3D"http://example.com">example.com</a>. IN A</div></blockquote><blockquote=
 style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div>AQ <a href=
=3D"http://example.com">example.com</a>. IN AAAA</div><div><br></div></bloc=
kquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px=
"><div>ANSWER <a href=3D"http://example.com">example.com</a>. 3600 IN MX 10=
 <a href=3D"http://mail.example.net">mail.example.net</a>.</div></blockquot=
e><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">AUT=
HORITY <a href=3D"http://example.com">example.com</a>. 3600 IN SOA =E2=80=
=A6</blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none;pa=
dding:0px"><div>ADDITIONAL . 0 CLASS4096 OPT ???</div></blockquote></div><d=
iv><br></div><div>In a more general sense, how are responders to generate=
=E2=80=94and how are initiators to interpret=E2=80=94responses in which it =
is not clear which question any given response record corresponds to?</div>=
<div><br></div><div>Section 3 defines the prefix field of an accompanying q=
uestion as &quot;a domain name with the form of a dot or a sequence of labe=
ls ending with a pointer&quot;... could you clarify that &quot;the form of =
a dot&quot; refers to the root domain name (i.e., a single null label with =
wire format 0x00)?</div><div><br></div><div>In section 4, what is meant by =
&quot;the responder assembles the prefix with the main domain name&quot;? W=
ire-format domain names are necessarily fully-qualified, whether or not the=
y end with compression pointers. Is the operation to be interpreted as some=
thing like &quot;if the prefix is the DNS root domain, treat it as the QNAM=
E&quot;? If so, I think such special processing is unnecessary, because it&=
#39;s already possible to reference the QNAME directly with a compression p=
ointer.</div><div><br></div><div>Why require accompanying question names to=
 match or be subdomains of the QNAME? It precludes potentially useful queri=
es like QNAME=3D<a href=3D"http://www.example.com">www.example.com</a>. acc=
ompanied by prefix=3D<a href=3D"http://static.example.com">static.example.c=
om</a>., and prohibiting them doesn&#39;t prevent out-of-bailiwick queries =
anyway.</div><div><br></div><div>Section 5 references a=C2=A0&quot;not been=
 implemented, too many accompanying-questions.&quot; response... what would=
 that response look like?</div><div><br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Sun, Sep 17, 2017 at 11:19 PM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_bla=
nk">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Domain Name System Operations WG of the IE=
TF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 A DNS Query including A Main Question with Accompanying Questions<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Jian=
kang Yao<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Paul Vixie<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ning Kong<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Xiaodong Li<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-yao=
-dnsop-accompanying-<wbr>questions-04.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 11<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-09-17<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document enables DNS initiators to send a main question<b=
r>
=C2=A0 =C2=A0accompanying with several related questions in a single DNS qu=
ery,<br>
=C2=A0 =C2=A0and enables DNS responders to put the answers into a single DN=
S<br>
=C2=A0 =C2=A0response.=C2=A0 This extension enables a range of initiators t=
o look up<br>
=C2=A0 =C2=A0&quot;X, or failing that, Y&quot; in a better way than both cu=
rrent<br>
=C2=A0 =C2=A0alternatives.=C2=A0 This mechanism can reduce the number of DN=
S round-<br>
=C2=A0 =C2=A0trips per application work-unit.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-yao-dnsop-accompanying-qu=
estions/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/<wbr>doc/draft-yao-dnsop-<wbr>accompanying-questions/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-yao-dnsop-accompanying-questio=
ns-04" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wb=
r>draft-yao-dnsop-accompanying-<wbr>questions-04</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-yao-dnsop-accompanyi=
ng-questions-04" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/<wbr>doc/html/draft-yao-dnsop-<wbr>accompanying-questions-04</a><br=
>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-yao-dnsop-accompanying=
-questions-04" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rf=
cdiff?<wbr>url2=3Ddraft-yao-dnsop-<wbr>accompanying-questions-04</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</a><br>
<br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
</blockquote></div><br></div>

--001a114fcaa080dcaf055981e431--


From nobody Tue Sep 19 09:50:10 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4764F134296; Tue, 19 Sep 2017 09:50:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150583980924.11770.7396631038774958095@ietfa.amsl.com>
Date: Tue, 19 Sep 2017 09:50:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gsq9WfvMwjGeOleZGpnEoqQd8ZU>
Subject: [DNSOP] I-D Action: draft-ietf-dnsop-rfc5011-security-considerations-05.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 16:50:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

        Title           : Security Considerations for RFC5011 Publishers
        Authors         : Wes Hardaker
                          Warren Kumari
	Filename        : draft-ietf-dnsop-rfc5011-security-considerations-05.txt
	Pages           : 14
	Date            : 2017-09-19

Abstract:
   This document extends the RFC5011 rollover strategy with timing
   advice that must be followed in order to maintain security.
   Specifically, this document describes the math behind the minimum
   time-length that a DNS zone publisher must wait before signing
   exclusively with recently added DNSKEYs.  It contains much math and
   complicated equations, but the summary is that the key rollover /
   revocation time is much longer than intuition would suggest.  If you
   are not both publishing a DNSSEC trust anchor, and using RFC5011 to
   update that trust anchor, you probably don't need to read this
   document.

   This document also describes the minimum time-length that a DNS zone
   publisher must wait after publishing a revoked DNSKEY before assuming
   that all active RFC5011 resolvers should have seen the revocation-
   marked key and removed it from their list of trust anchors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-rfc5011-security-considerations/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnsop-rfc5011-security-considerations-05
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc5011-security-considerations-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-rfc5011-security-considerations-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 20 00:45:56 2017
Return-Path: <yaojk@cnnic.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762081323B4 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 00:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 nzALNxUg4ZhM for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 00:45:51 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3409A126E64 for <dnsop@ietf.org>; Wed, 20 Sep 2017 00:45:48 -0700 (PDT)
Received: from healthyao-PC (unknown [218.241.103.239]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0A5QNCYHMJZFREKAA--.8353S2; Wed, 20 Sep 2017 15:45:28 +0800 (CST)
Date: Wed, 20 Sep 2017 15:45:27 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: "Richard Gibson" <rgibson@dyn.com>
Cc: dnsop <dnsop@ietf.org>
Reply-To: yaojk <yaojk@cnnic.cn>
References: <150570474802.613.6489161595724212264@ietfa.amsl.com>,  <CAC94RYbqkTFcK_cN8o6wXsxq6htBkaRHoGrCDiZ8bWvXexMstQ@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2017092015452073799670@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart710141677311_=----"
X-CM-TRANSID: AQAAf0A5QNCYHMJZFREKAA--.8353S2
X-Coremail-Antispam: 1UD129KBjvJXoW3Ar1UXFyxXF1rtw1UJF13Jwb_yoW7ur48pF W3Kr95KrykXrykGw1kG348WF1j93yfJrW7JFn5Gw1vv3s8uF1qvF18tF45ZFW7uFyft3y2 qw1UXw1kWa98ZFJanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUPab7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVWxJr0_GcWl84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202 j2C_Jr0_Gr1l5I8CrVAKz4kIr2xC04v26r1j6r4UMc02F40E42I26xC2a48xMcIj6xIIjx v20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1l F7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7xC0wCY02Avz4vE14v_GF4l42xK82 IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC2 0s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMI IF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF 0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4 A2jsIEc7CjxVAFwI0_Jr0_Gr1l6VACY4xI67k04243AbIYCTnIWIevJa73UjIFyTuYvjxU gVbkDUUUU
X-CM-SenderInfo: x1dryyw6fq0xffof0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wpet6k7LL5yPCvZPpSKC-1LTGDI>
Subject: Re: [DNSOP] I-D Action: draft-yao-dnsop-accompanying-questions-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 07:45:54 -0000

This is a multi-part message in MIME format.

------=_001_NextPart710141677311_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBSaWNoYXJkIEdpYnNvbiwNCg0KICAgICBUaGFua3MgYSBsb3QgZm9yIHlvdXIga2luZCBy
ZXZpZXcgYW5kIHF1ZXN0aW9ucy4NCg0KICAgICBzb21lIGNvbW1lbnRzIGFyZSBiZWxvdyBpbmxp
bmUuDQoNCg0KDQoNCkppYW5rYW5nIFlhbw0KDQpGcm9tOiBSaWNoYXJkIEdpYnNvbg0KRGF0ZTog
MjAxNy0wOS0xOSAxMDo0OA0KVG86IGRuc29wDQpTdWJqZWN0OiBSZTogW0ROU09QXSBJLUQgQWN0
aW9uOiBkcmFmdC15YW8tZG5zb3AtYWNjb21wYW55aW5nLXF1ZXN0aW9ucy0wNC50eHQNCkkgaGF2
ZSBzb21lIHF1ZXN0aW9ucyBhYm91dCB0aGlzIGRyYWZ0Lg0KDQoNCkhvdyBzaG91bGQgcmVzcG9u
ZGVycyBwb3B1bGF0ZSB0aGUgQ09VTlQgZmllbGRzIHdoZW4gb25lIHJlY29yZCBhbnN3ZXJzIG11
bHRpcGxlIGFjY29tcGFueWluZyBxdWVzdGlvbnM/IEZvciBleGFtcGxlLCBhc3N1bWUgZXhhbXBs
ZS5jb20gaGFzIGFuIE1YIHJlY29yZCBidXQgbm8gQSBvciBBQUFBICh0aGUgbGF0dGVyIHR3byB0
aHVzIGJlaW5nIGNvdmVyZWQgYnkgYW4gYXV0aG9yaXR5IHNlY3Rpb24gU09BKToNClFVRVNUSU9O
IGV4YW1wbGUuY29tLiBJTiBNWA0KQVEgZXhhbXBsZS5jb20uIElOIEENCkFRIGV4YW1wbGUuY29t
LiBJTiBBQUFBDQoNCg0KQU5TV0VSIGV4YW1wbGUuY29tLiAzNjAwIElOIE1YIDEwIG1haWwuZXhh
bXBsZS5uZXQuDQpBVVRIT1JJVFkgZXhhbXBsZS5jb20uIDM2MDAgSU4gU09BIOKApg0KICAgICAg
ICAgICAgICAgICAgICBleGFtcGxlLmNvbS4gMzYwMCBJTiBTT0Eg4oCmIA0KQURESVRJT05BTCAu
IDAgQ0xBU1M0MDk2IE9QVCA/Pz8NCg0KDQpJbiBhIG1vcmUgZ2VuZXJhbCBzZW5zZSwgaG93IGFy
ZSByZXNwb25kZXJzIHRvIGdlbmVyYXRl4oCUYW5kIGhvdyBhcmUgaW5pdGlhdG9ycyB0byBpbnRl
cnByZXTigJRyZXNwb25zZXMgaW4gd2hpY2ggaXQgaXMgbm90IGNsZWFyIHdoaWNoIHF1ZXN0aW9u
IGFueSBnaXZlbiByZXNwb25zZSByZWNvcmQgY29ycmVzcG9uZHMgdG8/DQoNCiANCltKaWFua2Fu
ZyBZYW9dIA0KICAgVGhlIHJlc3BvbmRlcnMgd2lsbCBwdXQgdGhlIHF1ZXJ5IHJlc3VsdCBvZiBt
YWluIHF1ZXN0aW9uIGZpcnN0LCB0aGVuIEFjY29tcGFueWluZyBRdWVzdGlvbiAxLCBBY2NvbXBh
bnlpbmcgUXVlc3Rpb24gMiBpbiB0aGUgYW5zd2VyLCBhdXRob3JpdHkgb3IgYWRkaXRpb25hbCBz
ZWN0aW9uLiBJdCBtZWFucyB0aGF0IHRoZSByZXNwb25kZXJzIHdpbGwgcHV0IHRoZSByZXN1bHRz
IGZvciBtYWluIHF1ZXN0aW9uIGZpcnN0LCB0aGVuIEFjY29tcGFueWluZyBRdWVzdGlvbiAxLCBB
Y2NvbXBhbnlpbmcgUXVlc3Rpb24gMiwgb25lIGJ5IG9uZSBpbiBvcmRlci4NCg0KICAgVGhlICBp
bml0aWF0b3JzIHdpbGwgYWxzbyBpbnRlcnByZXQgdGhlIHJlc3VsdCBpbiB0aGUgYW5zd2VyLCBh
dXRob3JpdHkgb3IgYWRkaXRpb25hbCBzZWN0aW9uLCBvbmUgcXVlc3Rpb24gYnkgb25lIHF1ZXN0
aW9uIGluIG9yZGVyLCBtYWluIHF1ZXN0aW9uIGZpcnN0LCB0aGVuIEFjY29tcGFueWluZyBRdWVz
dGlvbiAxLCBBY2NvbXBhbnlpbmcgUXVlc3Rpb24gMi4gVGhlIGludGVycHJldGF0aW9uIHdpbGwg
YmFzZSBvbiB0aGUgdmFsdWUgb2YgDQpBTkNPVU5ULCBBUkNPVU5ULCBOU0NPVU5ULCBhbmQgQVEt
QU5DT1VOVCwgQVEtQVJDT1VOVCwgQVEtTlNDT1VOVC4NCg0KSW4geW91ciBleGFtcGxlIGFib3Zl
LCAgDQpBTkNPVU5UPTEsIEFSQ09VTlQ9MSwgTlNDT1VOVD0wOw0KQVExLUFOQ09VTlQ9MCwgICBB
UTEtQVJDT1VOVD0wLCBBUTEtTlNDT1VOVD0xOw0KQVEyLUFOQ09VTlQ9MCwgQVEyLUFSQ09VTlQ9
MCwgQVExLU5TQ09VTlQ9MQ0KDQpzbyB0aGUgaW5pdGlhdG9ycyB3aWxsIGtub3c6DQp0aGUgcmVz
dWx0IGZvciBtYWluIHF1ZXN0aW9uIGlzOiAgICAgDQoNCiAgICAgQU5TV0VSIGV4YW1wbGUuY29t
LiAzNjAwIElOIE1YIDEwIG1haWwuZXhhbXBsZS5uZXQuDQogICAgIEFVVEhPUklUWSANCiAgICBB
RERJVElPTkFMIC4gMCBDTEFTUzQwOTYgT1BUID8/Pw0KDQp0aGUgcmVzdWx0IGZvciBhY2NvbXBh
bnlpbmcgcXVlc3Rpb24gMSBpczogDQoNCiAgICAgQU5TV0VSIA0KICAgIEFVVEhPUklUWSBleGFt
cGxlLmNvbS4gMzYwMCBJTiBTT0Eg4oCmDQogICAgQURESVRJT05BTCANCg0KdGhlIHJlc3VsdCBm
b3IgYWNjb21wYW55aW5nIHF1ZXN0aW9uIDIgaXM6IA0KDQogICBBTlNXRVIgDQogICBBVVRIT1JJ
VFkgZXhhbXBsZS5jb20uIDM2MDAgSU4gU09BIOKApg0KICAgQURESVRJT05BTCANCg0KIA0KDQoN
Cg0KDQpTZWN0aW9uIDMgZGVmaW5lcyB0aGUgcHJlZml4IGZpZWxkIG9mIGFuIGFjY29tcGFueWlu
ZyBxdWVzdGlvbiBhcyAiYSBkb21haW4gbmFtZSB3aXRoIHRoZSBmb3JtIG9mIGEgZG90IG9yIGEg
c2VxdWVuY2Ugb2YgbGFiZWxzIGVuZGluZyB3aXRoIGEgcG9pbnRlciIuLi4gY291bGQgeW91IGNs
YXJpZnkgdGhhdCAidGhlIGZvcm0gb2YgYSBkb3QiIHJlZmVycyB0byB0aGUgcm9vdCBkb21haW4g
bmFtZSAoaS5lLiwgYSBzaW5nbGUgbnVsbCBsYWJlbCB3aXRoIHdpcmUgZm9ybWF0IDB4MDApPw0K
W0ppYW5rYW5nIFlhb10gDQpzb3JyeSBmb3IgY29uZnVzaW9uIHdvcmRzLiBpdCBtZWFucyAgYSBz
aW5nbGUgbnVsbCBsYWJlbCAuDQoNCg0KIA0KDQpJbiBzZWN0aW9uIDQsIHdoYXQgaXMgbWVhbnQg
YnkgInRoZSByZXNwb25kZXIgYXNzZW1ibGVzIHRoZSBwcmVmaXggd2l0aCB0aGUgbWFpbiBkb21h
aW4gbmFtZSI/IFdpcmUtZm9ybWF0IGRvbWFpbiBuYW1lcyBhcmUgbmVjZXNzYXJpbHkgZnVsbHkt
cXVhbGlmaWVkLCB3aGV0aGVyIG9yIG5vdCB0aGV5IGVuZCB3aXRoIGNvbXByZXNzaW9uIHBvaW50
ZXJzLiBJcyB0aGUgb3BlcmF0aW9uIHRvIGJlIGludGVycHJldGVkIGFzIHNvbWV0aGluZyBsaWtl
ICJpZiB0aGUgcHJlZml4IGlzIHRoZSBETlMgcm9vdCBkb21haW4sIHRyZWF0IGl0IGFzIHRoZSBR
TkFNRSI/IElmIHNvLCBJIHRoaW5rIHN1Y2ggc3BlY2lhbCBwcm9jZXNzaW5nIGlzIHVubmVjZXNz
YXJ5LCBiZWNhdXNlIGl0J3MgYWxyZWFkeSBwb3NzaWJsZSB0byByZWZlcmVuY2UgdGhlIFFOQU1F
IGRpcmVjdGx5IHdpdGggYSBjb21wcmVzc2lvbiBwb2ludGVyLg0KW0ppYW5rYW5nIFlhb10gDQp0
aGFua3MsIFlvdSBhcmUgcmlnaHQuIEkgd2lsbCBjbGFyaWZ5IHRoZSB3b3Jkcy4NCg0KIA0KDQpX
aHkgcmVxdWlyZSBhY2NvbXBhbnlpbmcgcXVlc3Rpb24gbmFtZXMgdG8gbWF0Y2ggb3IgYmUgc3Vi
ZG9tYWlucyBvZiB0aGUgUU5BTUU/IEl0IHByZWNsdWRlcyBwb3RlbnRpYWxseSB1c2VmdWwgcXVl
cmllcyBsaWtlIFFOQU1FPXd3dy5leGFtcGxlLmNvbS4gYWNjb21wYW5pZWQgYnkgcHJlZml4PXN0
YXRpYy5leGFtcGxlLmNvbS4sIGFuZCBwcm9oaWJpdGluZyB0aGVtIGRvZXNuJ3QgcHJldmVudCBv
dXQtb2YtYmFpbGl3aWNrIHF1ZXJpZXMgYW55d2F5Lg0KW0ppYW5rYW5nIFlhb10gDQpjdXJyZW50
bHkgdGhlIHVzZSBjYXNlcyBmb3IgYWNjb21wYW55aW5nIHF1ZXN0aW9ucyBhcmUgdGhlIHNhbWUg
ZG9tYWluIG5hbWVzIHdpdGggZGlmZmVyZW50IHR5cHMgKEEgYW5kIEFBQSkgb3IgZGlmZmVyZW50
IHN1YiBkb21haW4gbmFtZXMgKFRMU0EgcmVjb3JkOiBfNDQzLl90Y3Aud3d3LmV4YW1wbGUuY29t
ICApLg0KDQpJZiB3ZSBjYW4gZmluZCBzb21lIHN0cm9uZyB1c2UgY2FzZXMgZm9yICBxdWVyaWVz
IGxpa2UgUU5BTUU9d3d3LmV4YW1wbGUuY29tLiBhY2NvbXBhbmllZCBieSBwcmVmaXg9c3RhdGlj
LmV4YW1wbGUuY29tLCB3ZSBtYXkgY29uc2lkZXIgdG8gYWRqdXN0IHRoZSBkZXNpZ24uDQoNCiAN
Cg0KDQpTZWN0aW9uIDUgcmVmZXJlbmNlcyBhICJub3QgYmVlbiBpbXBsZW1lbnRlZCwgdG9vIG1h
bnkgYWNjb21wYW55aW5nLXF1ZXN0aW9ucy4iIHJlc3BvbnNlLi4uIHdoYXQgd291bGQgdGhhdCBy
ZXNwb25zZSBsb29rIGxpa2U/DQpbSmlhbmthbmcgWWFvXSANCkhlcmUsIEkgdGhpbmsgdGhhdCBp
dCBuZWVkIGEgbmV3IHJjb2RlIHZhbHVlIGZvciBpdC4NCg0KDQoNCkJlc3QgUmVnYXJkcy4NCkpp
YW5rYW5nIFlhbw0KIA0KDQoNCg0KDQpPbiBTdW4sIFNlcCAxNywgMjAxNyBhdCAxMToxOSBQTSwg
PGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4gd3JvdGU6DQoNCg0KQSBOZXcgSW50ZXJuZXQtRHJh
ZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9y
aWVzLg0KVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgRG9tYWluIE5hbWUgU3lzdGVt
IE9wZXJhdGlvbnMgV0cgb2YgdGhlIElFVEYuDQoNCiAgICAgICAgVGl0bGUgICAgICAgICAgIDog
QSBETlMgUXVlcnkgaW5jbHVkaW5nIEEgTWFpbiBRdWVzdGlvbiB3aXRoIEFjY29tcGFueWluZyBR
dWVzdGlvbnMNCiAgICAgICAgQXV0aG9ycyAgICAgICAgIDogSmlhbmthbmcgWWFvDQogICAgICAg
ICAgICAgICAgICAgICAgICAgIFBhdWwgVml4aWUNCiAgICAgICAgICAgICAgICAgICAgICAgICAg
TmluZyBLb25nDQogICAgICAgICAgICAgICAgICAgICAgICAgIFhpYW9kb25nIExpDQogICAgICAg
IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LXlhby1kbnNvcC1hY2NvbXBhbnlpbmctcXVlc3Rpb25z
LTA0LnR4dA0KICAgICAgICBQYWdlcyAgICAgICAgICAgOiAxMQ0KICAgICAgICBEYXRlICAgICAg
ICAgICAgOiAyMDE3LTA5LTE3DQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVudCBlbmFibGVz
IEROUyBpbml0aWF0b3JzIHRvIHNlbmQgYSBtYWluIHF1ZXN0aW9uDQogICBhY2NvbXBhbnlpbmcg
d2l0aCBzZXZlcmFsIHJlbGF0ZWQgcXVlc3Rpb25zIGluIGEgc2luZ2xlIEROUyBxdWVyeSwNCiAg
IGFuZCBlbmFibGVzIEROUyByZXNwb25kZXJzIHRvIHB1dCB0aGUgYW5zd2VycyBpbnRvIGEgc2lu
Z2xlIEROUw0KICAgcmVzcG9uc2UuICBUaGlzIGV4dGVuc2lvbiBlbmFibGVzIGEgcmFuZ2Ugb2Yg
aW5pdGlhdG9ycyB0byBsb29rIHVwDQogICAiWCwgb3IgZmFpbGluZyB0aGF0LCBZIiBpbiBhIGJl
dHRlciB3YXkgdGhhbiBib3RoIGN1cnJlbnQNCiAgIGFsdGVybmF0aXZlcy4gIFRoaXMgbWVjaGFu
aXNtIGNhbiByZWR1Y2UgdGhlIG51bWJlciBvZiBETlMgcm91bmQtDQogICB0cmlwcyBwZXIgYXBw
bGljYXRpb24gd29yay11bml0Lg0KDQoNClRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdl
IGZvciB0aGlzIGRyYWZ0IGlzOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQteWFvLWRuc29wLWFjY29tcGFueWluZy1xdWVzdGlvbnMvDQoNClRoZXJlIGFyZSBhbHNvIGh0
bWxpemVkIHZlcnNpb25zIGF2YWlsYWJsZSBhdDoNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC15YW8tZG5zb3AtYWNjb21wYW55aW5nLXF1ZXN0aW9ucy0wNA0KaHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC15YW8tZG5zb3AtYWNjb21wYW55aW5nLXF1
ZXN0aW9ucy0wNA0KDQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFi
bGUgYXQ6DQpodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQteWFvLWRuc29w
LWFjY29tcGFueWluZy1xdWVzdGlvbnMtMDQNCg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0
YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQp1bnRp
bCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmll
dGYub3JnLg0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91
cyBGVFAgYXQ6DQpmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRE5TT1AgbWFpbGluZyBs
aXN0DQpETlNPUEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9kbnNvcA==

------=_001_NextPart710141677311_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DUTF-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20170920134903660953 {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; COLOR: #000000; FONT-SIZE: 10.5pt=
; 20307:=20
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: &#23435; COLOR: #000000; FONT-SIZE: 10.5pt=
; 20307:=20
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16684"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>Dear Richard&nbsp;Gibson,</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; Thanks a lot for your kind review and=20
questions.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; some comments are below inline.</DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN>Jiankang Yao</SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:rgibson@dyn.com">Richard Gibson</=
A></DIV>
<DIV><B>Date:</B>&nbsp;2017-09-19&nbsp;10:48</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:dnsop@ietf.org">dnsop</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [DNSOP] I-D Action:=20
draft-yao-dnsop-accompanying-questions-04.txt</DIV></DIV></DIV>
<DIV>
<DIV class=3DFoxDiv20170920134903660953>
<DIV dir=3Dltr>I have some questions about this draft.
<DIV><BR></DIV>
<DIV>How should responders populate the COUNT fields when one record answe=
rs=20
multiple accompanying questions? For example, assume <A=20
href=3D"http://example.com">example.com</A> has an MX record but no A or A=
AAA (the=20
latter two thus being covered by an authority section SOA):</DIV>
<DIV>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
  <DIV>QUESTION <A href=3D"http://example.com">example.com</A>. IN=20
MX</DIV></BLOCKQUOTE>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
  <DIV>AQ <A href=3D"http://example.com">example.com</A>. IN A</DIV></BLOC=
KQUOTE>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
  <DIV>AQ <A href=3D"http://example.com">example.com</A>. IN AAAA</DIV>
  <DIV><BR></DIV></BLOCKQUOTE>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
  <DIV>ANSWER <A href=3D"http://example.com">example.com</A>. 3600 IN MX 1=
0 <A=20
  href=3D"http://mail.example.net">mail.example.net</A>.</DIV></BLOCKQUOTE=
>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">AUT=
HORITY=20
  <A href=3D"http://example.com">example.com</A>. 3600 IN SOA =E2=80=A6<BR=
><SPAN><FONT=20
  style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt=
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;<A href=3D"http://example.com/">example.com</A><FONT color=3D#0000=
00>. 3600=20
  IN SOA =E2=80=A6</FONT>&nbsp;</FONT></SPAN></BLOCKQUOTE>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px;=
 BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
  <DIV>ADDITIONAL . 0 CLASS4096 OPT ???</DIV></BLOCKQUOTE></DIV>
<DIV><BR></DIV>
<DIV>In a more general sense, how are responders to generate=E2=80=94and h=
ow are=20
initiators to interpret=E2=80=94responses in which it is not clear which q=
uestion any=20
given response record corresponds to?<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<BR>&nbsp;</FONT></SPAN><BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;<BR>&nbsp;&nbsp;&nbsp;The responders will put the&nbsp;query=
=20
result of main question first, then&nbsp;Accompanying&nbsp;Question=20
1,&nbsp;Accompanying Question&nbsp;2 in the answer, authority or additiona=
l=20
section. It means that the responders will put the results for main questi=
on=20
first, then Accompanying Question 1, Accompanying Question 2, one by one i=
n=20
order.<BR><BR>&nbsp;&nbsp;&nbsp;The <FONT=20
color=3D#000000>&nbsp;initiators&nbsp;will also interpret=20
the&nbsp;result&nbsp;</FONT><FONT color=3D#1f497d>in the answer, authority=
 or=20
additional section, one question by one question in order, main question f=
irst,=20
then Accompanying Question 1, Accompanying Question 2. The interpretation =
will=20
base on the value of&nbsp;<BR><FONT color=3D#000000>ANCOUNT, ARCOUNT, NSCO=
UNT,=20
and&nbsp;AQ-ANCOUNT, AQ-ARCOUNT, AQ-NSCOUNT.<BR></FONT></FONT><BR>In&nbsp;=
your=20
example above,&nbsp;&nbsp;<BR><FONT color=3D#000000>ANCOUNT=3D1, ARCOUNT=
=3D1,=20
NSCOUNT=3D0;<BR>AQ1-ANCOUNT=3D0,&nbsp;&nbsp;&nbsp;AQ1-ARCOUNT=3D0,=20
AQ1-NSCOUNT=3D1;<BR>AQ2-ANCOUNT=3D0, AQ2-ARCOUNT=3D0, AQ1-NSCOUNT=3D1<BR><=
BR>so the=20
initiators will know:<BR>the&nbsp;result for main question=20
is:&nbsp;&nbsp;&nbsp;&nbsp; <BR>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;=20
ANSWER&nbsp;example.com.&nbsp;3600&nbsp;IN&nbsp;MX&nbsp;10&nbsp;mail.examp=
le.net.</DIV>
<DIV>&nbsp;&nbsp;&nbsp; &nbsp;AUTHORITY&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;=20
ADDITIONAL&nbsp;.&nbsp;0&nbsp;CLASS4096&nbsp;OPT&nbsp;???</DIV><BR>the res=
ult=20
for&nbsp;accompanying question 1&nbsp;is: <BR>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp; ANSWER&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;=20
AUTHORITY&nbsp;example.com.&nbsp;3600&nbsp;IN&nbsp;SOA&nbsp;=E2=80=A6</DIV=
>
<DIV>&nbsp;&nbsp;&nbsp; ADDITIONAL&nbsp;<BR><BR>the result for accompanyin=
g=20
question&nbsp;2 is: <BR>
<DIV>&nbsp;&nbsp; ANSWER </DIV>
<DIV>&nbsp;&nbsp; AUTHORITY example.com. 3600 IN SOA =E2=80=A6</DIV>
<DIV>&nbsp;&nbsp;=20
ADDITIONAL&nbsp;<BR></FONT><BR>&nbsp;<BR><BR></FONT></SPAN></DIV></DIV></D=
IV>
<DIV><BR>&nbsp;</DIV>
<DIV>Section 3 defines the prefix field of an accompanying question as "a =
domain=20
name with the form of a dot or a sequence of labels ending with a pointer"=
...=20
could you clarify that "the form of a dot" refers to the root domain name =
(i.e.,=20
a single null label with wire format 0x00)?<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;<BR>sorry for confusion words. it&nbsp;means&nbsp;&nbsp;<FON=
T=20
color=3D#000000>a single null label .<BR></FONT></FONT></SPAN></DIV>
<DIV><BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
&nbsp;</FONT></SPAN><BR></DIV>
<DIV>In section 4, what is meant by "the responder assembles the prefix wi=
th the=20
main domain name"? Wire-format domain names are necessarily fully-qualifie=
d,=20
whether or not they end with compression pointers. Is the operation to be=20
interpreted as something like "if the prefix is the DNS root domain, treat=
 it as=20
the QNAME"? If so, I think such special processing is unnecessary, because=
 it's=20
already possible to reference the QNAME directly with a compression=20
pointer.<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;<BR>thanks, You are right. I will clarify the=20
words.<BR><BR>&nbsp;</FONT></SPAN><BR></DIV>
<DIV>Why require accompanying question names to match or be subdomains of =
the=20
QNAME? It precludes potentially useful queries like QNAME=3D<A=20
href=3D"http://www.example.com">www.example.com</A>. accompanied by prefix=
=3D<A=20
href=3D"http://static.example.com">static.example.com</A>., and prohibitin=
g them=20
doesn't prevent out-of-bailiwick queries anyway.<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;<BR>currently the use cases for accompanying questions are=20
the&nbsp;same domain names with different typs (A and AAA)&nbsp;or differe=
nt sub=20
domain names (TLSA record: <FONT=20
color=3D#000000>_443._tcp.www.example.com&nbsp;</FONT>&nbsp;).<BR><BR>If w=
e can=20
find some strong use cases for&nbsp;<FONT color=3D#000000> queries like=20
QNAME=3D</FONT><A href=3D"http://www.example.com/">www.example.com</A><FON=
T=20
color=3D#000000>. accompanied by prefix=3D</FONT><A=20
href=3D"http://static.example.com/">static.example.com</A>, we may conside=
r to=20
adjust the design.<BR><BR>&nbsp;</FONT></SPAN></DIV>
<DIV><BR></DIV>
<DIV>Section 5 references a&nbsp;"not been implemented, too many=20
accompanying-questions." response... what would that response look=20
like?<BR><SPAN><FONT=20
style=3D"FONT-FAMILY: Times New Roman; COLOR: #1f497d; FONT-SIZE: 10.5pt">=
<I>[Jiankang=20
Yao]</I>&nbsp;<BR>Here, I think that it need a new rcode value for=20
it.<BR><BR><BR><BR>Best Regards.<BR>Jiankang Yao<BR>&nbsp;</FONT></SPAN></=
DIV>
<DIV><BR></DIV></DIV>
<DIV class=3Dgmail_extra><BR>
<DIV class=3Dgmail_quote>On Sun, Sep 17, 2017 at 11:19 PM, <SPAN dir=3Dltr=
>&lt;<A=20
href=3D"mailto:internet-drafts@ietf.org"=20
target=3D_blank>internet-drafts@ietf.org</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-L=
EFT: 1ex"=20
class=3Dgmail_quote><BR>A New Internet-Draft is available from the on-line=
=20
  Internet-Drafts directories.<BR>This draft is a work item of the Domain =
Name=20
  System Operations WG of the IETF.<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;=20
  Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: A DNS Query including A =
Main=20
  Question with Accompanying Questions<BR>&nbsp; &nbsp; &nbsp; &nbsp;=20
  Authors&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Jiankang Yao<BR>&nbsp; &nbsp;=
=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
  Paul Vixie<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; Ning Kong<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Xiaodong Li<BR>&=
nbsp;=20
  &nbsp; &nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; :=20
  draft-yao-dnsop-accompanying-<WBR>questions-04.txt<BR>&nbsp; &nbsp; &nbs=
p;=20
  &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 11<BR>&nbsp; &nbs=
p;=20
  &nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; :=20
  2017-09-17<BR><BR>Abstract:<BR>&nbsp; &nbsp;This document enables DNS=20
  initiators to send a main question<BR>&nbsp; &nbsp;accompanying with sev=
eral=20
  related questions in a single DNS query,<BR>&nbsp; &nbsp;and enables DNS=
=20
  responders to put the answers into a single DNS<BR>&nbsp;=20
  &nbsp;response.&nbsp; This extension enables a range of initiators to lo=
ok=20
  up<BR>&nbsp; &nbsp;"X, or failing that, Y" in a better way than both=20
  current<BR>&nbsp; &nbsp;alternatives.&nbsp; This mechanism can reduce th=
e=20
  number of DNS round-<BR>&nbsp; &nbsp;trips per application=20
  work-unit.<BR><BR><BR>The IETF datatracker status page for this draft=20
  is:<BR><A=20
  href=3D"https://datatracker.ietf.org/doc/draft-yao-dnsop-accompanying-qu=
estions/"=20
  rel=3Dnoreferrer=20
  target=3D_blank>https://datatracker.ietf.org/<WBR>doc/draft-yao-dnsop-<W=
BR>accompanying-questions/</A><BR><BR>There=20
  are also htmlized versions available at:<BR><A=20
  href=3D"https://tools.ietf.org/html/draft-yao-dnsop-accompanying-questio=
ns-04"=20
  rel=3Dnoreferrer=20
  target=3D_blank>https://tools.ietf.org/html/<WBR>draft-yao-dnsop-accompa=
nying-<WBR>questions-04</A><BR><A=20
  href=3D"https://datatracker.ietf.org/doc/html/draft-yao-dnsop-accompanyi=
ng-questions-04"=20
  rel=3Dnoreferrer=20
  target=3D_blank>https://datatracker.ietf.org/<WBR>doc/html/draft-yao-dns=
op-<WBR>accompanying-questions-04</A><BR><BR>A=20
  diff from the previous version is available at:<BR><A=20
  href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-yao-dnsop-accompanying=
-questions-04"=20
  rel=3Dnoreferrer=20
  target=3D_blank>https://www.ietf.org/rfcdiff?<WBR>url2=3Ddraft-yao-dnsop=
-<WBR>accompanying-questions-04</A><BR><BR><BR>Please=20
  note that it may take a couple of minutes from the time of submission<BR=
>until=20
  the htmlized version and diff are available at <A href=3D"http://tools.i=
etf.org"=20
  rel=3Dnoreferrer target=3D_blank>tools.ietf.org</A>.<BR><BR>Internet-Dra=
fts are=20
  also available by anonymous FTP at:<BR><A=20
  href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3Dnoreferrer=20
  target=3D_blank>ftp://ftp.ietf.org/internet-<WBR>drafts/</A><BR><BR>____=
__________________________<WBR>_________________<BR>DNSOP=20
  mailing list<BR><A href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</A><BR>=
<A=20
  href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3Dnoreferrer=20
  target=3D_blank>https://www.ietf.org/mailman/<WBR>listinfo/dnsop</A><BR>=
</BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BODY></HTML>

------=_001_NextPart710141677311_=------



From nobody Wed Sep 20 10:29:48 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E489F13232C for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 10:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oJuMoiqbgDd9 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 10:29:43 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD609124207 for <dnsop@ietf.org>; Wed, 20 Sep 2017 10:29:43 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id z8so3136740itc.2 for <dnsop@ietf.org>; Wed, 20 Sep 2017 10:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nQn4vvL6bqDgzIhMO+AH/kaOD0v/JWTs9RtzCJqSrTY=; b=lrNu107y+9TxQ6FKUmeiLlnZjJB2leNUiTML/pluZj7o7TczWMz1ufcVIkBY2wj+8I V8NqBOoXkXtwWB8bcybtUbSHVCrGvphLs90blWfm8+PjfmQ8dv3s/iGrLnvpiwjWefrG kGy+RocyybtPNMLH/IXBZV8erinVVdfPWJdF/6UThtiEB0/rj1qPEYJJKLz4+m42hCAR NnEeCACwCi+5ufgOfzXycppD6ILAd2xvmEAEj6wkarDQYuXDg0MM3LCP5Hvj4ZRQL3nw VxqahLrV5ssmFr2A6QkWIsc1QQrRz3DIvNblvrIJj6gWmBGIL4biaQKmbcuQbjfZm4VZ Gl0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nQn4vvL6bqDgzIhMO+AH/kaOD0v/JWTs9RtzCJqSrTY=; b=sdLq3rOHSJCWx0N/Rc8364azF4AaMQ70LBB8WA+ggJQo2sJc9cnY5Vol6gbrzyculp 1v1JxCMPFUc3Nj2IzhkOJ615UEBJSIBjplvvFBQEfs/U9R+Bd7HAxgaoTRhLmV9REi7C fqMWYG1fGfybUxw2XPrr+xIOUlMdMWh2klKg+eLm136JKohmnM1VrRxB5zVWMHrDarrj pYNvWGeYEJd5wmtOftS6GPEUtu4vXBHJ1cW6I3NnxZ1bfxKbsH2j7/9gmnm5Jy8oiUor 545Ih7n64q8YXamz6stdPwDDAxSE/yM9j1Ha5sXhl9zW50PxiR9jiREyYbAp+q3qFQht 6w2A==
X-Gm-Message-State: AHPjjUi/0jq7sCat6aIpMRsfqo9UNyuLJCTmsYjsspFmQ+YveP6Xn5Fh TnQDIdceWUVwPijAeWfI2XVOf6WIzXdwCAu16kw=
X-Google-Smtp-Source: AOwi7QCWYBWwwmUsByOc+ifLCGTCqO62FTpky9ql4pDiMlk5txV9hbXXoMF050V+9GKQDFoVYTkBHCXYwvVzSHhhhDI=
X-Received: by 10.36.31.200 with SMTP id d191mr4103557itd.81.1505928582854; Wed, 20 Sep 2017 10:29:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.22.2 with HTTP; Wed, 20 Sep 2017 10:29:42 -0700 (PDT)
In-Reply-To: <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com>
From: william manning <chinese.apricot@gmail.com>
Date: Wed, 20 Sep 2017 10:29:42 -0700
Message-ID: <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11446e863cfbb80559a25288"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iqsoFeVZqjumOECeHrI385ZCzQk>
Subject: Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-resp-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 17:29:46 -0000

--001a11446e863cfbb80559a25288
Content-Type: text/plain; charset="UTF-8"

i think this is a worthy document for consideration.

/Wm

On Sun, Sep 10, 2017 at 9:29 PM, Davey Song <songlinjian@gmail.com> wrote:

> Hi folks,
>
> I just submit a draft dealing with issue of large DNS response especially
> in IPv6. Commnets are welcome.
>
> If chairs think it is in the scope of dnsop wg and encourage us to discuss
> it in this mailing list, I can submit it as a draft listed in dnsop wg.
>
> Davey
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: 11 September 2017 at 10:13
> Subject: I-D Action: draft-song-atr-large-resp-00.txt
> To: i-d-announce@ietf.org
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : ATR: Additional Truncated Response for Large DNS
> Response
>         Author          : Linjian Song
>         Filename        : draft-song-atr-large-resp-00.txt
>         Pages           : 8
>         Date            : 2017-09-10
>
> Abstract:
>    As the increasing use of DNSSEC and IPv6, there are more public
>    evidence and concerns on IPv6 fragmentation issues due to larger DNS
>    payloads over IPv6.  This memo introduces an simple improvement on
>    authoritative server by replying additional truncated response just
>    after the normal large response.
>
>    REMOVE BEFORE PUBLICATION: The source of the document with test
>    script is currently placed at GitHub [ATR-Github].  Comments and pull
>    request are welcome.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-song-atr-large-resp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-song-atr-large-resp-00
> https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft
> <https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>
> directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

--001a11446e863cfbb80559a25288
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">i think this is a worthy document for consideration. =C2=
=A0<div><br></div><div>/Wm</div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Sun, Sep 10, 2017 at 9:29 PM, Davey Song <span dir=
=3D"ltr">&lt;<a href=3D"mailto:songlinjian@gmail.com" target=3D"_blank">son=
glinjian@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr"><div>Hi folks,=C2=A0</div><div><br></div><div>I just submi=
t a draft dealing with issue of large DNS response especially in IPv6. Comm=
nets are welcome.=C2=A0</div><div><br></div><div>If chairs think it is in t=
he scope of dnsop wg and encourage us to discuss it in this mailing list, I=
 can submit it as a draft listed in dnsop wg.</div><div><br></div><div>Dave=
y</div><div>=C2=A0=C2=A0</div><br><div class=3D"gmail_quote">---------- For=
warded message ----------<br>From: <b class=3D"gmail_sendername"></b> <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_bla=
nk">internet-drafts@ietf.org</a>&gt;</span><br>Date: 11 September 2017 at 1=
0:13<br>Subject: I-D Action: draft-song-atr-large-resp-00.<wbr>txt<br>To: <=
a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce@ietf=
.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 ATR: Additional Truncated Response for Large DNS Response<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Linj=
ian Song<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-son=
g-atr-large-resp-00.t<wbr>xt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 8<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-09-10<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0As the increasing use of DNSSEC and IPv6, there are more publi=
c<br>
=C2=A0 =C2=A0evidence and concerns on IPv6 fragmentation issues due to larg=
er DNS<br>
=C2=A0 =C2=A0payloads over IPv6.=C2=A0 This memo introduces an simple impro=
vement on<br>
=C2=A0 =C2=A0authoritative server by replying additional truncated response=
 just<br>
=C2=A0 =C2=A0after the normal large response.<br>
<br>
=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the document with tes=
t<br>
=C2=A0 =C2=A0script is currently placed at GitHub [ATR-Github].=C2=A0 Comme=
nts and pull<br>
=C2=A0 =C2=A0request are welcome.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-song-atr-large-resp/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr>oc/dra=
ft-song-atr-large-resp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-song-atr-large-resp-00" rel=3D=
"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>aft-song-=
atr-large-resp-00</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-=
00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr=
>oc/html/draft-song-atr-large-r<wbr>esp-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
<br>
______________________________<wbr>_________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announce@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>i=
stinfo/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shadow.htm<wbr>l<=
/a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel=3D"noreferrer"=
 target=3D"_blank">ftp://ftp.ietf.org/ietf/1shado<wbr>w-sites.txt</a><br>
</div><br></div>
<br>______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
<br></blockquote></div><br></div>

--001a11446e863cfbb80559a25288--


From nobody Wed Sep 20 16:47:11 2017
Return-Path: <rgibson@dyn.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F419132396 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 16:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dyn.com
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 XQG9WO0ZAyyr for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 16:47:08 -0700 (PDT)
Received: from mail-ua0-x246.google.com (mail-ua0-x246.google.com [IPv6:2607:f8b0:400c:c08::246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 010EF1321BB for <dnsop@ietf.org>; Wed, 20 Sep 2017 16:47:08 -0700 (PDT)
Received: by mail-ua0-x246.google.com with SMTP id 72so3504684uas.7 for <dnsop@ietf.org>; Wed, 20 Sep 2017 16:47:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dyn.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kRvolV98sa6tQD4BuSMGYuC2X7k1tYx2jVtWrGDIZTo=; b=pKwTIDmEGD1I0N7BLx0jK04gAtGxiYBIuxaYXPXhPIf3dk4LZ0Mq+nn/1g4/Ay4Qg0 rMw2ewSNm8V8LI/tWBPUh+BvDVzD60bx1VzTRLz2ZkcesUMBzfsrGo7/RJ+ZOOC6I6Ih h5zl3JxYYIIKHV+XMyWvfRKWkxWiAI4abCGuM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kRvolV98sa6tQD4BuSMGYuC2X7k1tYx2jVtWrGDIZTo=; b=KKNGIFiS3bCKzbpWjSmAWV7Ytc/cfZ57QLu6/GY/s3jw2TGTW0fJBQZy64s2Vu8g6t erXUd+Bm1+wNe03VEwayJp+J9F2Kc53OV3Feti+126WmtRuSk8pQFfyveDFO4J8D02M2 PqmMRxoCEyXr9RNWvHfZ4HMIHoI4ZIYRo12s6Nk95FuL4ssAuDQJYk41knWVOvpIacWR mozQOck2Ljf7YSPl5znDz3fbSrGKC/wNedxGZiXFy1nQ0/wVLaC8A9lit8+jMS/4ZF0c QQmmlm85ruM7ERELJq16StWzXoZ+5oKnf/Q4F3QQKHolh0IEzSgz+WSKkhUex5ExMJu0 l9Zg==
X-Gm-Message-State: AHPjjUjx+V/w1mZKvxBeIEfnMOcHVuABfL3/uwVQ5kKO2gGZ4410Ddug AZ/a3A2c6PQl79Srh7dT4zhKKVLLYUt0u2VnYAq3Z9F6aOw=
X-Google-Smtp-Source: AOwi7QAiC/KPjvCz5zGXXvS39FMNf8f6JGpBcEfUy/ifnuleWRRPYHMlO1SURS3ZHlQR68duykfu+ACcux8AOi6KdNw=
X-Received: by 10.31.170.15 with SMTP id t15mr302766vke.155.1505951227056; Wed, 20 Sep 2017 16:47:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.62.136 with HTTP; Wed, 20 Sep 2017 16:46:46 -0700 (PDT)
In-Reply-To: <2017092015452073799670@cnnic.cn>
References: <150570474802.613.6489161595724212264@ietfa.amsl.com> <CAC94RYbqkTFcK_cN8o6wXsxq6htBkaRHoGrCDiZ8bWvXexMstQ@mail.gmail.com> <2017092015452073799670@cnnic.cn>
From: Richard Gibson <rgibson@dyn.com>
Date: Wed, 20 Sep 2017 19:46:46 -0400
Message-ID: <CAC94RYb2JqbQQH=CeHyFpPesDGDZhk7nOB5jCa51SZYSH4J0kQ@mail.gmail.com>
To: yaojk <yaojk@cnnic.cn>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11432250f02a3b0559a7977a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/agxZ38czdqaz8PP_8Zv0j5qrSRo>
Subject: Re: [DNSOP] I-D Action: draft-yao-dnsop-accompanying-questions-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 23:47:10 -0000

--001a11432250f02a3b0559a7977a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 20, 2017 at 3:45 AM, Jiankang Yao <yaojk@cnnic.cn> wrote:

> *From:* Richard Gibson <rgibson@dyn.com>
> *Date:* 2017-09-19 10:48
> *To:* dnsop <dnsop@ietf.org>
> *Subject:* Re: [DNSOP] I-D Action: draft-yao-dnsop-accompanying-
> questions-04.txt
> In a more general sense, how are responders to generate=E2=80=94and how a=
re
> initiators to interpret=E2=80=94responses in which it is not clear which =
question
> any given response record corresponds to?
>
>
> *[Jiankang Yao]*
>    The responders will put the query result of main question first,
> then Accompanying Question 1, Accompanying Question 2 in the answer,
> authority or additional section. It means that the responders will put th=
e
> results for main question first, then Accompanying Question 1, Accompanyi=
ng
> Question 2, one by one in order.
>
Ah, so the response is expected to include *duplicate* records when they
answer multiple questions (e.g., in the case of NXDOMAIN and NODATA
results)? That's worth making explicit (e.g., rewording "the SOA resource
record will be put in the authority section" in section 4). And I believe
it also calls for guidance instructing responders to reject question sets
that include duplicates or special QTYPES (AXFR/IXFR/ANY), including a
description of *how* to reject (e.g., AQ-RCODE=3DREFUSED).

> Why require accompanying question names to match or be subdomains of the
> QNAME? It precludes potentially useful queries like QNAME=3Dwww.example.c=
om.
> accompanied by prefix=3Dstatic.example.com., and prohibiting them doesn't
> prevent out-of-bailiwick queries anyway.
> *[Jiankang Yao]*
> currently the use cases for accompanying questions are the same domain
> names with different typs (A and AAA) or different sub domain names (TLSA
> record: _443._tcp.www.example.com  ).
>
> If we can find some strong use cases for  queries like QNAME=3D
> www.example.com. accompanied by prefix=3Dstatic.example.com, we may
> consider to adjust the design.
>
 I don't think you need to adjust the design, just strike "The domain name
for accompanying questions MUST be same with the domain name for a main
question or be children name of it" from section 3.

Your response did get me thinking about name compression, though. RFC 3597
section 4 <https://tools.ietf.org/html/rfc3597#section-4> states "Future
specifications for new RR types that contain domain names within their
RDATA MUST NOT allow the use of name compression for those names", and I
don't think that should be tossed aside lightly. If they truly are to be
allowed in EDNS0 options (which may already be a mistake), I think that
they MUST be required to point into the first QNAME of the message.

--001a11432250f02a3b0559a7977a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Sep 20, 2017 at 3:45 AM, Jiankang Yao <span dir=3D"ltr">&lt;<a href=3D"=
mailto:yaojk@cnnic.cn" target=3D"_blank">yaojk@cnnic.cn</a>&gt;</span> wrot=
e:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div style=3D"margin:10px">
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-bottom-color:initial;border-left-color:initial;padding:3pt 0cm 0cm;bo=
rder-top-color:rgb(181,196,223);border-right-color:initial">
<div style=3D"padding:8px;background:rgb(239,239,239);color:rgb(0,0,0);font=
-size:12px">
<div><b>From:</b>=C2=A0<a href=3D"mailto:rgibson@dyn.com" target=3D"_blank"=
>Richard Gibson</a></div>
<div><b>Date:</b>=C2=A02017-09-19=C2=A010:48</div>
<div><b>To:</b>=C2=A0<a href=3D"mailto:dnsop@ietf.org" target=3D"_blank">dn=
sop</a></div>
<div><b>Subject:</b>=C2=A0Re: [DNSOP] I-D Action:=20
draft-yao-dnsop-accompanying-<wbr>questions-04.txt</div></div></div>
<div>
<div class=3D"gmail-m_6997491177104436028FoxDiv20170920134903660953">
<div dir=3D"ltr"><div><span class=3D"gmail-">In a more general sense, how a=
re responders to generate=E2=80=94and how are=20
initiators to interpret=E2=80=94responses in which it is not clear which qu=
estion any=20
given response record corresponds to?<br><span><font style=3D"font-family:&=
quot;Times New Roman&quot;;color:rgb(31,73,125);font-size:10.5pt"><br>=C2=
=A0</font></span><br></span><span><font style=3D"font-family:&quot;Times Ne=
w Roman&quot;;color:rgb(31,73,125);font-size:10.5pt"><i>[Jiankang=20
Yao]</i>=C2=A0<br>=C2=A0=C2=A0=C2=A0The responders will put the=C2=A0query=
=20
result of main question first, then=C2=A0Accompanying=C2=A0Question=20
1,=C2=A0Accompanying Question=C2=A02 in the answer, authority or additional=
=20
section. It means that the responders will put the results for main questio=
n=20
first, then Accompanying Question 1, Accompanying Question 2, one by one in=
=20
order.<br></font></span></div></div></div></div></div></blockquote><div>Ah,=
 so the response is expected to include=C2=A0<i>duplicate</i>=C2=A0records =
when they answer multiple questions (e.g., in the case of NXDOMAIN and NODA=
TA results)? That&#39;s worth making explicit (e.g., rewording &quot;the SO=
A resource record will be put in the authority section&quot; in section 4).=
 And I believe it also calls for guidance instructing responders to reject =
question sets that include duplicates or special QTYPES (AXFR/IXFR/ANY), in=
cluding a description of <i>how</i>=C2=A0to reject (e.g., AQ-RCODE=3DREFUSE=
D).</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"ma=
rgin:10px"><div><div class=3D"gmail-m_6997491177104436028FoxDiv201709201349=
03660953"><div dir=3D"ltr">Why require accompanying question names to match=
 or be subdomains of the=20
QNAME? It precludes potentially useful queries like QNAME=3D<a href=3D"http=
://www.example.com" target=3D"_blank">www.example.com</a>. accompanied by p=
refix=3D<a href=3D"http://static.example.com" target=3D"_blank">static.exam=
ple.com</a>., and prohibiting them=20
doesn&#39;t prevent out-of-bailiwick queries anyway.<br></div></div><div><s=
pan><font style=3D"font-family:&quot;Times New Roman&quot;;color:rgb(31,73,=
125);font-size:10.5pt"><i>[Jiankang=20
Yao]</i>=C2=A0<br>currently the use cases for accompanying questions are=20
the=C2=A0same domain names with different typs (A and AAA)=C2=A0or differen=
t sub=20
domain names (TLSA record: <font color=3D"#000000">_443._<a href=3D"http://=
tcp.www.example.com" target=3D"_blank">tcp.www.example.com</a>=C2=A0</font>=
=C2=A0).<br><br>If we can=20
find some strong use cases for=C2=A0<font color=3D"#000000"> queries like=
=20
QNAME=3D</font><a href=3D"http://www.example.com/" target=3D"_blank">www.ex=
ample.com</a><font color=3D"#000000">. accompanied by prefix=3D</font><a hr=
ef=3D"http://static.example.com/" target=3D"_blank">static.example.com</a>,=
 we may consider to=20
adjust the design.<br></font></span></div></div></div></blockquote><div>=C2=
=A0I don&#39;t think you need to adjust the design, just strike &quot;The d=
omain name for accompanying questions MUST be same with the domain name for=
 a main question or be children name of it&quot; from section 3.</div><div>=
<br></div><div>Your response did get me thinking about name compression, th=
ough. <a href=3D"https://tools.ietf.org/html/rfc3597#section-4">RFC 3597 se=
ction 4</a> states &quot;Future specifications for new RR types that contai=
n domain names within their RDATA MUST NOT allow the use of name compressio=
n for those names&quot;, and I don&#39;t think that should be tossed aside =
lightly. If they truly are to be allowed in EDNS0 options (which may alread=
y be a mistake), I think that they MUST be required to point into the first=
 QNAME of the message.</div></div></div></div>

--001a11432250f02a3b0559a7977a--


From nobody Wed Sep 20 17:06:38 2017
Return-Path: <Jeff.Hodges@kingsmountain.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E841321BB for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 17:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 IEVt0aY7Nbl6 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 17:06:35 -0700 (PDT)
Received: from qproxy1-pub.mail.unifiedlayer.com (qproxy1-pub.mail.unifiedlayer.com [173.254.64.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2BC012ECEC for <dnsop@ietf.org>; Wed, 20 Sep 2017 17:06:35 -0700 (PDT)
Received: from cmgw3 (unknown [10.0.90.84]) by qproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 457451202FC for <dnsop@ietf.org>; Wed, 20 Sep 2017 18:06:35 -0600 (MDT)
Received: from box514.bluehost.com ([74.220.219.114]) by cmgw3 with  id C06Y1w00C2UhLwi0106bje; Wed, 20 Sep 2017 18:06:35 -0600
X-Authority-Analysis: v=2.2 cv=K/VSJ2eI c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=IkcTkHD0fZMA:10 a=2JCJgTwv5E4A:10 a=48vgC7mUAAAA:8 a=o1Ym26DpRQwWE5MmH5MA:9 a=QEXdDO2ut3YA:10 a=w1C3t2QeGrPiZgrLijVG:22
Received: from c-73-202-80-238.hsd1.ca.comcast.net ([73.202.80.238]:51578 helo=[192.168.11.53]) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1dup0h-000S1i-Tz for dnsop@ietf.org; Wed, 20 Sep 2017 18:06:32 -0600
To: IETF DNSOP WG <dnsop@ietf.org>
From: =JeffH <Jeff.Hodges@KingsMountain.com>
Message-ID: <b1f0105a-314a-8ffa-d8ff-d8359bc2348a@KingsMountain.com>
Date: Wed, 20 Sep 2017 17:06:30 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box514.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - KingsMountain.com
X-BWhitelist: no
X-Source-IP: 73.202.80.238
X-Exim-ID: 1dup0h-000S1i-Tz
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: c-73-202-80-238.hsd1.ca.comcast.net ([192.168.11.53]) [73.202.80.238]:51578
X-Source-Auth: jeff.hodges+kingsmountain.com
X-Email-Count: 1
X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ==
X-Local-Domain: no
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XXadBmj981rtPW8p9y2Qs4etuNA>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 00:06:37 -0000

 > This starts a formal Call for Adoption for
 > draft-west-let-localhost-be-localhost
 >
 > The draft is available here:
 > <https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/>
 >
 >  Please review this draft to see if you think it is suitable for
 > adoption by DNSOP, and comments to the list, clearly stating your
 > view.

I support adoption of this draft, with the understanding that the 
working group needs to come to rough consensus on some of the 
(subtle-but-important) details within.

Am willing to review, tho am not a DNS expert. Upon reading through the 
-06 rev and this thread, it seems overall good-to-go to me modulo 
resolving said subtle-but-important details.

HTH,

=JeffH




From nobody Wed Sep 20 20:22:47 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F13132F69 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.331
X-Spam-Level: 
X-Spam-Status: No, score=-1.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 Y_73Xdk5-ZX0 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:22:41 -0700 (PDT)
Received: from smtpbg291.qq.com (smtpbg291.qq.com [113.108.11.223]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 104851321DF for <dnsop@ietf.org>; Wed, 20 Sep 2017 20:22:40 -0700 (PDT)
X-QQ-mid: bizesmtp8t1505964133tl0cniqeg
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Thu, 21 Sep 2017 11:22:12 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: xcDtUgrDx+MWrACr/HgPYXK6V64fjhNBCv6eC1e7cSvGbsNEKow2ucCeeam3F QwJTewvNrcpwQMQRKbRyyQ2UnMt58DbjENzlmcw9n7w6JWWHwJSGVEZFi7gvu5ApKq7BDjI Fa/VMdofFuz2DRHPA0fqkHPOq1OO6zWUV/rOTSvmAG0PeB9888EtJjPLCM6XPmw/gqEq99c ZNia3Z25vJ4i/Vbh72Quzz8XmUDZeXEkJyFr9hfEjjC7s0W/LQBkxl0ewpYkd9l+JbDG02H YQH3hql9bkpsplmK2Cq4ldIzke1MQWUIJXssCQMYMoKvVRNg8GSj93qkPlpwEiPcNzKcIfV NDWmxQ55hmhVILENqLle/CuHJjG8w==
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'william manning'" <chinese.apricot@gmail.com>, "'Davey Song'" <songlinjian@gmail.com>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com>
In-Reply-To: <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com>
Date: Thu, 21 Sep 2017 11:22:16 +0800
Message-ID: <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_045C_01D332CB.E21E1AD0"
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: zh-cn
Thread-Index: AdMyNhLdlVMcCUVlQ6u1PwsyYcgYnAAUV1kA
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgweb:qybgweb12
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vNHg7AGWZs1FUKLAXt7C7DkuT6Q>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgRndkOiBJLUQgQWN0aW9uOiBkcmFmdC1z?= =?utf-8?q?ong-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 03:22:46 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_045C_01D332CB.E21E1AD0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you.=20

=20

The large DNS response in IPv6 is a real problem. ATR is one option to =
adopted in authoritative  server alone. If someone or party have more =
influence on both resolver and authoritative side (cloud and app =
provider who can choose their own DNS resolution path),  =
Mukund=E2=80=99s proposal to fragment the DNS message is a good =
solution.   =
https://tools.ietf.org/html/draft-muks-dns-message-fragments-00=20

=20

So I do recommend ATR and DNS message fragments should be both =
considered  in a tool box for large DNS response issues.=20

=20

Davey =20

=20

=E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:dnsop-bounces@ietf.org] =
=E4=BB=A3=E8=A1=A8 william manning
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B49=E6=9C=8821=E6=97=A5 =
1:30
=E6=94=B6=E4=BB=B6=E4=BA=BA: Davey Song
=E6=8A=84=E9=80=81: dnsop
=E4=B8=BB=E9=A2=98: Re: [DNSOP] Fwd: I-D Action: =
draft-song-atr-large-resp-00.txt

=20

i think this is a worthy document for consideration. =20

=20

/Wm

=20

On Sun, Sep 10, 2017 at 9:29 PM, Davey Song <songlinjian@gmail.com> =
wrote:

Hi folks,=20

=20

I just submit a draft dealing with issue of large DNS response =
especially in IPv6. Commnets are welcome.=20

=20

If chairs think it is in the scope of dnsop wg and encourage us to =
discuss it in this mailing list, I can submit it as a draft listed in =
dnsop wg.

=20

Davey

 =20

=20

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 11 September 2017 at 10:13
Subject: I-D Action: draft-song-atr-large-resp-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts =
directories.


        Title           : ATR: Additional Truncated Response for Large =
DNS Response
        Author          : Linjian Song
        Filename        : draft-song-atr-large-resp-00.txt
        Pages           : 8
        Date            : 2017-09-10

Abstract:
   As the increasing use of DNSSEC and IPv6, there are more public
   evidence and concerns on IPv6 fragmentation issues due to larger DNS
   payloads over IPv6.  This memo introduces an simple improvement on
   authoritative server by replying additional truncated response just
   after the normal large response.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [ATR-Github].  Comments and pull
   request are welcome.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-song-atr-large-resp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-song-atr-large-resp-00
https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-00


Please note that it may take a couple of minutes from the time of =
submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce =
<https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>=20
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=20


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

=20


------=_NextPart_000_045C_01D332CB.E21E1AD0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;
	font-family:=E5=AE=8B=E4=BD=93;}
span.HTMLChar
	{mso-style-name:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F";
	font-family:=E5=AE=8B=E4=BD=93;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thank you. <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><pre><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The large DNS response in IPv6 is a real problem. ATR is one option =
to adopted in authoritative =C2=A0server alone. If someone or party have =
more influence on both resolver and authoritative side (cloud and app =
provider who can choose their own DNS resolution path), =
=C2=A0Mukund=E2=80=99s proposal to fragment the DNS message is a good =
solution.=C2=A0=C2=A0 <a =
href=3D"https://tools.ietf.org/html/draft-muks-dns-message-fragments-00">=
https://tools.ietf.org/html/draft-muks-dns-message-fragments-00</a> =
</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;color:black'><o:p></o:p></span></pre><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So I do recommend ATR and DNS message fragments should be both =
considered =C2=A0in a tool box for large DNS response issues. =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Davey =C2=A0<o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3D"_MailEndCompose"><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></a></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt'>=E5=8F=91=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt'> DNSOP [mailto:dnsop-bounces@ietf.org] =
</span><b><span style=3D'font-size:10.0pt'>=E4=BB=A3=E8=A1=A8 =
</span></b><span lang=3DEN-US style=3D'font-size:10.0pt'>william =
manning<br></span><b><span =
style=3D'font-size:10.0pt'>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4<span =
lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt'> 2017</span><span =
style=3D'font-size:10.0pt'>=E5=B9=B4<span =
lang=3DEN-US>9</span>=E6=9C=88<span lang=3DEN-US>21</span>=E6=97=A5<span =
lang=3DEN-US> 1:30<br></span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> Davey =
Song<br></span><b>=E6=8A=84=E9=80=81<span lang=3DEN-US>:</span></b><span =
lang=3DEN-US> dnsop<br></span><b>=E4=B8=BB=E9=A2=98<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> Re: [DNSOP] Fwd: I-D =
Action: =
draft-song-atr-large-resp-00.txt<o:p></o:p></span></span></p></div></div>=
<p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-US>i think this is a worthy document for consideration. =
&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US>/Wm<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-US>On Sun, Sep 10, 2017 at 9:29 PM, =
Davey Song &lt;<a href=3D"mailto:songlinjian@gmail.com" =
target=3D"_blank">songlinjian@gmail.com</a>&gt; =
wrote:<o:p></o:p></span></p><div><div><p class=3DMsoNormal><span =
lang=3DEN-US>Hi folks,&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>I just submit a draft dealing with =
issue of large DNS response especially in IPv6. Commnets are =
welcome.&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>If chairs think it is in the scope =
of dnsop wg and encourage us to discuss it in this mailing list, I can =
submit it as a draft listed in dnsop =
wg.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US>Davey<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;&nbsp;<o:p></o:p></span></p></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-US>---------- Forwarded message =
----------<br>From: &lt;<a href=3D"mailto:internet-drafts@ietf.org" =
target=3D"_blank">internet-drafts@ietf.org</a>&gt;<br>Date: 11 September =
2017 at 10:13<br>Subject: I-D Action: =
draft-song-atr-large-resp-00.txt<br>To: <a =
href=3D"mailto:i-d-announce@ietf.org" =
target=3D"_blank">i-d-announce@ietf.org</a><br><br><br><br>A New =
Internet-Draft is available from the on-line Internet-Drafts =
directories.<br><br><br>&nbsp; &nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;: ATR: Additional Truncated Response for =
Large DNS Response<br>&nbsp; &nbsp; &nbsp; &nbsp; Author&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; : Linjian Song<br>&nbsp; &nbsp; &nbsp; &nbsp; =
Filename&nbsp; &nbsp; &nbsp; &nbsp; : =
draft-song-atr-large-resp-00.txt<br>&nbsp; &nbsp; &nbsp; &nbsp; =
Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 8<br>&nbsp; &nbsp; =
&nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : =
2017-09-10<br><br>Abstract:<br>&nbsp; &nbsp;As the increasing use of =
DNSSEC and IPv6, there are more public<br>&nbsp; &nbsp;evidence and =
concerns on IPv6 fragmentation issues due to larger DNS<br>&nbsp; =
&nbsp;payloads over IPv6.&nbsp; This memo introduces an simple =
improvement on<br>&nbsp; &nbsp;authoritative server by replying =
additional truncated response just<br>&nbsp; &nbsp;after the normal =
large response.<br><br>&nbsp; &nbsp;REMOVE BEFORE PUBLICATION: The =
source of the document with test<br>&nbsp; &nbsp;script is currently =
placed at GitHub [ATR-Github].&nbsp; Comments and pull<br>&nbsp; =
&nbsp;request are welcome.<br><br><br>The IETF datatracker status page =
for this draft is:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-song-atr-large-resp/" =
target=3D"_blank">https://datatracker.ietf.org/doc/draft-song-atr-large-r=
esp/</a><br><br>There are also htmlized versions available at:<br><a =
href=3D"https://tools.ietf.org/html/draft-song-atr-large-resp-00" =
target=3D"_blank">https://tools.ietf.org/html/draft-song-atr-large-resp-0=
0</a><br><a =
href=3D"https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-0=
0" =
target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-song-atr-la=
rge-resp-00</a><br><br><br>Please note that it may take a couple of =
minutes from the time of submission<br>until the htmlized version and =
diff are available at <a href=3D"http://tools.ietf.org" =
target=3D"_blank">tools.ietf.org</a>.<br><br>Internet-Drafts are also =
available by anonymous FTP at:<br><a =
href=3D"ftp://ftp.ietf.org/internet-drafts/" =
target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br><br>________=
_______________________________________<br>I-D-Announce mailing =
list<br><a href=3D"mailto:I-D-Announce@ietf.org" =
target=3D"_blank">I-D-Announce@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft"=
 =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d-announce<br>I=
nternet-Draft</a> directories: <a =
href=3D"http://www.ietf.org/shadow.html" =
target=3D"_blank">http://www.ietf.org/shadow.html</a><br>or <a =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
target=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><o:p></o:p=
></span></p></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
lang=3DEN-US><br>_______________________________________________<br>DNSOP=
 mailing list<br><a =
href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/dnsop" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><o:p></o=
:p></span></p></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></div></body></html>
------=_NextPart_000_045C_01D332CB.E21E1AD0--


From nobody Wed Sep 20 20:44:39 2017
Return-Path: <wseltzer@w3.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A0A133075 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 dtded3_pwz8F for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:44:36 -0700 (PDT)
Received: from raoul.w3.org (raoul.w3.org [IPv6:2001:470:8b2d:804:52:12:128:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1A441201F8 for <dnsop@ietf.org>; Wed, 20 Sep 2017 20:44:35 -0700 (PDT)
Received: from pool-74-104-152-165.bstnma.fios.verizon.net ([74.104.152.165] helo=[192.168.86.32]) by raoul.w3.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <wseltzer@w3.org>) id 1dusPk-0008V6-6k; Thu, 21 Sep 2017 03:44:36 +0000
To: tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
References: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
From: Wendy Seltzer <wseltzer@w3.org>
Organization: W3C
Message-ID: <5bc2ff65-ad88-b4bc-d26f-3e433d57ee3c@w3.org>
Date: Wed, 20 Sep 2017 23:44:33 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+EZQY9i5-4Ce-NZykwC+sS6iY868Wg0crW6KAZTGQxFQg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/WEi83WsIKbRgvWo9rO9xOPdkbvs>
Subject: Re: [DNSOP] DNSOP Call for Adoption - draft-west-let-localhost-be-localhost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 03:44:38 -0000

>From a W3C perspective, and for the further specification of components
of the web security model, it would be helpful to have this behavior of
the loopback interface specified.

I support adoption and will be willing to review text.

Thanks,
--Wendy

On 09/06/2017 10:00 AM, tjw ietf wrote:
> When the idea of having a Call for Adoption for this document came up, we
> thought long and hard about this one.  However, the comments from the
> working group focused this document to address the specific issue of the
> local hostname.
> 
> This starts a formal Call for Adoption for
> draft-west-let-localhost-be-localhost
> 
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-west-let-localhost-be-localhost/
> 
> Please review this draft to see if you think it is suitable for adoption by
> DNSOP, and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.
> 
> This call for adoption ends: 20 September 2017
> 
> Thanks,
> tim wicinski
> DNSOP co-chair


-- 
Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
Strategy Lead, World Wide Web Consortium (W3C)
https://wendy.seltzer.org/        +1.617.863.0613 (mobile)



From nobody Wed Sep 20 20:45:40 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648D61330AE for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=QUsifVND; dkim=pass (1024-bit key) header.d=yitter.info header.b=Oue8Or4I
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 4UY63CqL44gj for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 20:45:37 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B76B01201F8 for <dnsop@ietf.org>; Wed, 20 Sep 2017 20:45:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 1C657BEDA1 for <dnsop@ietf.org>; Thu, 21 Sep 2017 03:45:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1505965537; bh=38c7VkKeZTtwy/iAxaiv5LORsex9q6a4ujz5a0KRb/4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=QUsifVNDTP8Y07yNEaY3J5/x70EVxe2sS7wUKsrOJYf48lG63T92Swqol+YpAY0wS 4PYsbx1UwAS8eRmnCOABObGgtiinYA6AwETA5nLLFnQnlWH9nFkKJ+FvxlLvsC7Orp kTh+RKaX8XDxbZHzHV5pIFgIHspEdZ9pNS0gCjw4=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRjSYx8l5kAz for <dnsop@ietf.org>; Thu, 21 Sep 2017 03:45:35 +0000 (UTC)
Date: Wed, 20 Sep 2017 23:45:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1505965535; bh=38c7VkKeZTtwy/iAxaiv5LORsex9q6a4ujz5a0KRb/4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Oue8Or4Ip/6j6FkBfKInRa+xjtvDJMu+9M2VtsA50S5MrErqO/eFTKC1NVRcG6KEA 7z9Eg6TKHmIipyt+RFnheE01VuEiEg+GoBbrFVChqMLj8gZBv2krJ/1mF4hOJxMCxz vSD+YfMO4QFgFa91+GzOd/cm0WIHnWxvBTmzBkB0=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170921034533.d2isi2idl7cyepea@mx4.yitter.info>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170824142147.lshdlmjv62nojd32@nic.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jXl6yIy8gcHPHGTbJAlWcGpT_Ro>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 03:45:39 -0000

Hi,

The conversation on QNAME went quiet some time ago, so I thought it
might be a good time to send a proposal about what to say about this
term.  I haven't passed this by my co-editors, since it seems like
we're going all to need to discuss anyway.

Here's the old text:

   QNAME  The most commonly-used definition is that the QNAME is a field
      in the Question section of a query.  "A standard query specifies a
      target domain name (QNAME), query type (QTYPE), and query class
      (QCLASS) and asks for RRs which match."  (Quoted from [RFC1034],
      Section 3.7.1.)

      [RFC2308], however, has an alternate definition that puts the
      QNAME in the answer (or series of answers) instead of the query.
      It defines QNAME as: "...the name in the query section of an
      answer, or where this resolves to a CNAME, or CNAME chain, the
      data field of the last CNAME.  The last CNAME in this sense is
      that which contains a value which does not resolve to another
      CNAME."

Here's a proposal to replace it:

   QNAME  The most commonly-used rough definition is that the QNAME is a
      field in the Question section of a query.  "A standard query
      specifies a target domain name (QNAME), query type (QTYPE), and
      query class (QCLASS) and asks for RRs which match."  (Quoted from
      [RFC1034], Section 3.7.1.).  Strictly speaking, the definition
      comes from [RFC1035], Section 4.1.2, where the QNAME is defined in
      respect of the Question Section.  This definition appears to be
      applied consistently: the discussion of inverse queries in section
      6.4 refers to the "owner name of the query RR and its TTL",
      because inverse queries populate the Answer Section and leave the
      Question Section empty.  (Inverse queries are deprecated in
      [RFC3425], and so relevant definitions do not appear in this
      memo.)

      [RFC2308], however, has an alternate definition that puts the
      QNAME in the answer (or series of answers) instead of the query.
      It defines QNAME as: "...the name in the query section of an
      answer, or where this resolves to a CNAME, or CNAME chain, the
      data field of the last CNAME.  The last CNAME in this sense is
      that which contains a value which does not resolve to another
      CNAME."  This definition has a certain internal logic, because of
      the way CNAME substitution works and the definition of CNAME.  If
      a name server does not find an RRset that matches a query, but it
      finds the same name in the same class with a CNAME record, then
      the name server "includes the CNAME record in the response and
      restarts the query at the domain name specified in the data field
      of the CNAME record."  ([RFC1034] Section 3.6.2).  This is made
      explicit in the resolution algorithm outlined in Section 4.3.2,
      which says to "change QNAME to the canonical name in the CNAME RR,
      and go back to step 1" in the case of a CNAME RR.  Since a CNAME
      record explicitly declares that the owner name is canonically
      named what is in the RDATA, then there is a way to view the new
      name (i.e. the name that was in the RDATA of the CNAME RR) as also
      being the QNAME.

      This creates a kind of confusion, however, because the answer to a
      query that results in CNAME processing contains in the echoed
      Question Section one QNAME (the name in the original query), and a
      second QNAME that is in the data field of the last CNAME.  The
      confusion comes from the iterative/recursive mode of resolution,
      which finally returns an answer that need not actually have the
      same owner name as the QNAME contained in the original query.

      To address this potential confusion, it is helpful to distinguish
      between two meanings:
      
      QNAME (original)  The name actually sent in the Question
         Section in the orignal query, which is always echoed in the
         (final) reply in the Question Section when the QR bit is set to
         1.

      QNAME (effective)  The name actually resolved, which is either the
         name actually queried or else the last name in a CNAME chain as
         defined in [RFC2308].

I'm certainly not wedded to these two names.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Sep 20 21:50:29 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1DF1342C2 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 21:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 61WziwjRHOP5 for <dnsop@ietfa.amsl.com>; Wed, 20 Sep 2017 21:50:25 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF54C124239 for <dnsop@ietf.org>; Wed, 20 Sep 2017 21:50:25 -0700 (PDT)
Received: from [10.0.0.23] (pool-173-79-98-3.washdc.fios.verizon.net [173.79.98.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id D1EC161FA2; Thu, 21 Sep 2017 04:50:24 +0000 (UTC)
Message-ID: <59C34510.4080705@redbarn.org>
Date: Wed, 20 Sep 2017 21:50:24 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>
CC: 'william manning' <chinese.apricot@gmail.com>,  'Davey Song' <songlinjian@gmail.com>, 'dnsop' <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A
In-Reply-To: <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xpzsTO2_6l9hdOCq3x2szklvKA8>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgRndkOiBJLUQgQWN0aW9uOiBkcmFmdC1z?= =?utf-8?q?ong-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 04:50:27 -0000

Davey Song(宋林健) wrote:
> Thank you.
>
> The large DNS response in IPv6 is a real problem. ATR is one option
> to adopted in authoritative  server alone. If someone or party have
> more influence on both resolver and authoritative side (cloud and app
> provider who can choose their own DNS resolution path),  Mukund’s
> proposal to fragment the DNS message is a good
> solution.https://tools.ietf.org/html/draft-muks-dns-message-fragments-00

both ideas are wrong. what we have to do is arrange to fragment, using 
the ipv6 extension header, all ipv6 udp, for a period of not less than 
five years. noone who blocks ipv6 extension headers should be able to 
get reliable ipv6 udp services. we have to make this problem felt where 
it is made. we must NOT work around it to insulate the makers of the 
problem from the costs of their actions.

> So I do recommend ATR and DNS message fragments should be both
> considered  in a tool box for large DNS response issues.

can a freebsd kernel hacker please contact me? i need some patches, but 
i'm traveling extensively, and i can't do the investigation and software 
engineering myself.

-- 
P Vixie


From nobody Thu Sep 21 00:08:51 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B91A133058 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.132
X-Spam-Level: 
X-Spam-Status: No, score=-4.132 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 1L0V7s2r7YLN for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:08:45 -0700 (PDT)
Received: from smtpbgau1.qq.com (smtpbgau1.qq.com [54.206.16.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CBDF132D14 for <dnsop@ietf.org>; Thu, 21 Sep 2017 00:08:43 -0700 (PDT)
X-QQ-mid: bizesmtp1t1505977708t788o90ls
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Thu, 21 Sep 2017 15:08:27 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: HITE0aRZYMIw0Vtx4vp/Ms2w/4c9H5dvArH8/2H9pzm3CjBCjHysqrlTjXW+d 6Xrcv/a9FUEXDosvPVLXd+XR1J/Re6yqY/P5k2UOfLf2EZzClPaksBsmhsmd7lPGCtpFCPx LrgwzTwuGKYGWGfV88gpucWk+MLHkyuxEDTLY6QyBzumDxGgduxNfvOxWN6l5ZstEIHYOli 6pIRcs+a4JMHn5OpeMv6jGiurGAixWgVRaQYEMt486ena1OqV0dwEITknke4GIyh9Ko7Jgk ZL9N4prQXY/6mNJbx7i+ql+1/SJKXQ/ZBrF13whg0wgEPh06szEmi8dPCqZ8YVDey2Ww==
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'Paul Vixie'" <paul@redbarn.org>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org>
In-Reply-To: <59C34510.4080705@redbarn.org>
Date: Thu, 21 Sep 2017 15:08:32 +0800
Message-ID: <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: zh-cn
Thread-Index: AdMylSqYcRRWl0ePQz6huodDIi97mwADcoHg
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/v68VMKYAGE6ECYwWOBDinmgjWjY>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 07:08:50 -0000

Hi Paul,=20

I know you suggest expose the problem and let the trouble maker feeling =
the pain themselves. But return to the specific issue, from APNIC's =
measurement the ASes in the path are dropping the fragments, rather than =
end ASes. From these ASes' view , it's your pain not theirs.=20

In another word, we are facing the fragmented and uncooperative =
Internet. What should we do ? It is very hard to coordinate all parts =
and networks. DNS is a field with lots of tussle.

Davey

> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:dnsop-bounces@ietf.org] =
=E4=BB=A3=E8=A1=A8 Paul Vixie
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2017=E5=B9=B49=E6=9C=8821=E6=97=A5 12:50
> =E6=94=B6=E4=BB=B6=E4=BA=BA: "Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5)"
> =E6=8A=84=E9=80=81: 'Davey Song'; 'dnsop'; 'william manning'
> =E4=B8=BB=E9=A2=98: Re: [DNSOP] =E7=AD=94=E5=A4=8D: Fwd: I-D Action: =
draft-song-atr-large-resp-00.txt
>=20
>=20
>=20
> Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) wrote:
> > Thank you.
> >
> > The large DNS response in IPv6 is a real problem. ATR is one option =
to
> > adopted in authoritative  server alone. If someone or party have =
more
> > influence on both resolver and authoritative side (cloud and app
> > provider who can choose their own DNS resolution path),  =
Mukund=E2=80=99s
> > proposal to fragment the DNS message is a good
> > =
solution.https://tools.ietf.org/html/draft-muks-dns-message-fragments-
> > 00
>=20
> both ideas are wrong. what we have to do is arrange to fragment, using =
the
> ipv6 extension header, all ipv6 udp, for a period of not less than =
five years.
> noone who blocks ipv6 extension headers should be able to get reliable =
ipv6 udp
> services. we have to make this problem felt where it is made. we must =
NOT
> work around it to insulate the makers of the problem from the costs of =
their
> actions.
>=20
> > So I do recommend ATR and DNS message fragments should be both
> > considered  in a tool box for large DNS response issues.
>=20
> can a freebsd kernel hacker please contact me? i need some patches, =
but i'm
> traveling extensively, and i can't do the investigation and software =
engineering
> myself.
>=20
> --
> P Vixie
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop




From nobody Thu Sep 21 00:09:05 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F237134325 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.352
X-Spam-Level: 
X-Spam-Status: No, score=-1.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 7__6f50WJ-xw for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:08:53 -0700 (PDT)
Received: from smtpbguseast3.qq.com (smtpbguseast3.qq.com [54.243.244.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5209133058 for <dnsop@ietf.org>; Thu, 21 Sep 2017 00:08:52 -0700 (PDT)
X-QQ-mid: bizesmtp1t1505977708t788o90ls
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Thu, 21 Sep 2017 15:08:27 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: HITE0aRZYMIw0Vtx4vp/Ms2w/4c9H5dvArH8/2H9pzm3CjBCjHysqrlTjXW+d 6Xrcv/a9FUEXDosvPVLXd+XR1J/Re6yqY/P5k2UOfLf2EZzClPaksBsmhsmd7lPGCtpFCPx LrgwzTwuGKYGWGfV88gpucWk+MLHkyuxEDTLY6QyBzumDxGgduxNfvOxWN6l5ZstEIHYOli 6pIRcs+a4JMHn5OpeMv6jGiurGAixWgVRaQYEMt486ena1OqV0dwEITknke4GIyh9Ko7Jgk ZL9N4prQXY/6mNJbx7i+ql+1/SJKXQ/ZBrF13whg0wgEPh06szEmi8dPCqZ8YVDey2Ww==
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'Paul Vixie'" <paul@redbarn.org>
Cc: "'dnsop'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org>
In-Reply-To: <59C34510.4080705@redbarn.org>
Date: Thu, 21 Sep 2017 15:08:32 +0800
Message-ID: <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: zh-cn
Thread-Index: AdMylSqYcRRWl0ePQz6huodDIi97mwADcoHg
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/v68VMKYAGE6ECYwWOBDinmgjWjY>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 07:08:57 -0000

Hi Paul,=20

I know you suggest expose the problem and let the trouble maker feeling =
the pain themselves. But return to the specific issue, from APNIC's =
measurement the ASes in the path are dropping the fragments, rather than =
end ASes. From these ASes' view , it's your pain not theirs.=20

In another word, we are facing the fragmented and uncooperative =
Internet. What should we do ? It is very hard to coordinate all parts =
and networks. DNS is a field with lots of tussle.

Davey

> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: DNSOP [mailto:dnsop-bounces@ietf.org] =
=E4=BB=A3=E8=A1=A8 Paul Vixie
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2017=E5=B9=B49=E6=9C=8821=E6=97=A5 12:50
> =E6=94=B6=E4=BB=B6=E4=BA=BA: "Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5)"
> =E6=8A=84=E9=80=81: 'Davey Song'; 'dnsop'; 'william manning'
> =E4=B8=BB=E9=A2=98: Re: [DNSOP] =E7=AD=94=E5=A4=8D: Fwd: I-D Action: =
draft-song-atr-large-resp-00.txt
>=20
>=20
>=20
> Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) wrote:
> > Thank you.
> >
> > The large DNS response in IPv6 is a real problem. ATR is one option =
to
> > adopted in authoritative  server alone. If someone or party have =
more
> > influence on both resolver and authoritative side (cloud and app
> > provider who can choose their own DNS resolution path),  =
Mukund=E2=80=99s
> > proposal to fragment the DNS message is a good
> > =
solution.https://tools.ietf.org/html/draft-muks-dns-message-fragments-
> > 00
>=20
> both ideas are wrong. what we have to do is arrange to fragment, using =
the
> ipv6 extension header, all ipv6 udp, for a period of not less than =
five years.
> noone who blocks ipv6 extension headers should be able to get reliable =
ipv6 udp
> services. we have to make this problem felt where it is made. we must =
NOT
> work around it to insulate the makers of the problem from the costs of =
their
> actions.
>=20
> > So I do recommend ATR and DNS message fragments should be both
> > considered  in a tool box for large DNS response issues.
>=20
> can a freebsd kernel hacker please contact me? i need some patches, =
but i'm
> traveling extensively, and i can't do the investigation and software =
engineering
> myself.
>=20
> --
> P Vixie
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop




From nobody Thu Sep 21 00:22:24 2017
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4183132EA7 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 UYucuxp480Ts for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 00:22:21 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76DB21326ED for <dnsop@ietf.org>; Thu, 21 Sep 2017 00:22:21 -0700 (PDT)
Received: from [10.43.15.103] (unknown [78.154.124.20]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 163F42421249; Thu, 21 Sep 2017 07:22:19 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <048701d332a8$6f944980$4ebcdc80$@cn>
Date: Thu, 21 Sep 2017 08:22:17 +0100
Cc: Paul Vixie <paul@redbarn.org>, dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7173DD0A-5B97-48F4-98A1-417FFC11C3D6@rfc1035.com>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>
To: =?utf-8?Q?=22Davey_Song=28=E5=AE=8B=E6=9E=97=E5=81=A5=29=22?= <ljsong@biigroup.cn>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tNSCOV-79M4WwerqzzRPUXilYYs>
Subject: [DNSOP] a fragmented and uncooperative Internet
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 07:22:23 -0000

> On 21 Sep 2017, at 08:08, Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) =
<ljsong@biigroup.cn> wrote:
>=20
> In another word, we are facing the fragmented and uncooperative =
Internet. What should we do ?

Switch it off? Hand it over to ITU control? :-)

The Internet was designed from the outset to work around breakage. =
Packet fragmentation issues will always be with us unfortunately. The =
networks which have these problems will fix them: Darwinism will take =
care of that eventually. Until then everyone else just has to work =
around them or ignore their brokenness. 'coz that's how it works.

We (for some definition of we) might come up with some tools to help =
identify the problem or do some outreach and education to help mend =
these broken networks. However I am sceptical those sort of things will =
be successful. After all we still have nets, servers and middleboxes =
that can't/won't handle EDNS correctly or assume that DNS packets only =
ever go over UDP and are always < 512 bytes.


From nobody Thu Sep 21 02:26:11 2017
Return-Path: <ljsong@biigroup.cn>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152A61345DF for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 02:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.132
X-Spam-Level: 
X-Spam-Status: No, score=-4.132 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, INVALID_MSGID=0.568, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 FW5Ax2uu3Fv8 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 02:26:05 -0700 (PDT)
Received: from smtpproxy19.qq.com (smtpproxy19.qq.com [184.105.206.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E1F1345E3 for <dnsop@ietf.org>; Thu, 21 Sep 2017 02:26:04 -0700 (PDT)
X-QQ-mid: bizesmtp5t1505985959tbnprr91g
Received: from sljpc (unknown [118.145.7.179]) by esmtp4.qq.com (ESMTP) with  id ; Thu, 21 Sep 2017 17:25:58 +0800 (CST)
X-QQ-SSF: 00400000004000F0FxF0000A0000000
X-QQ-FEAT: 9MsTBLS6yXEvSwSQ4q1DDXrU5Z2AU0b7kX16N2PCt1gW707yW6otKWVkQ54dj qTd5hoP1APzgN7Fdzg4pctkN8uzEwJjIIGf4nrtV9cT09ZH6c0csY45biszyO7ZbFzS+zq3 OdH4dz7ZFDYuJa17a2JQUulFowVxpcLGWZHsfC7nVvLCnAM8Pj7VyeGNQU4m1hP113U/FsV E+qrQMWxQFeF9Q8zN4VKodxIiDuGeTUTfZZrbL9XL5t9RABd2q08SQSQ8FLHc/dYy4F8oCZ ksO8JiPH0OolQHE2B9xhDvE8KemaoGzZZxrbAp6tChblYZPLG6EpWIk5g=
X-QQ-GoodBg: 2
From: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
To: "'Jim Reid'" <jim@rfc1035.com>
Cc: "'Paul Vixie'" <paul@redbarn.org>, "'dnsop WG'" <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn> <7173DD0A-5B97-48F4-98A1-417FFC11C3D6@rfc1035.com>
In-Reply-To: <7173DD0A-5B97-48F4-98A1-417FFC11C3D6@rfc1035.com>
Date: Thu, 21 Sep 2017 17:26:02 +0800
Message-ID: <04b201d332bb$a5184260$ef48c720$@cn>+03F671168742430C
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: zh-cn
Thread-Index: AdMyql0AbrLKO0owQ/WgRNmIDnNe9AAEQulw
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:biigroup.cn:qybgforeign:qybgforeign4
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YOgT5JWMBm9wiqDTkOuZ-ou8LWI>
Subject: [DNSOP] =?utf-8?b?562U5aSNOiBhIGZyYWdtZW50ZWQgYW5kIHVuY29vcGVy?= =?utf-8?q?ative_Internet?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 09:26:10 -0000

OK. I finally understand the context of the word " Darwinism " in many =
IETF discussion and slides. Haha~

Davey
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Jim Reid [mailto:jim@rfc1035.com]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2017=E5=B9=B49=E6=9C=8821=E6=97=A5 15:22
> =E6=94=B6=E4=BB=B6=E4=BA=BA: "Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5)"
> =E6=8A=84=E9=80=81: Paul Vixie; dnsop WG
> =E4=B8=BB=E9=A2=98: a fragmented and uncooperative Internet
>=20
>=20
> > On 21 Sep 2017, at 08:08, Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) =
<ljsong@biigroup.cn> wrote:
> >
> > In another word, we are facing the fragmented and uncooperative =
Internet.
> What should we do ?
>=20
> Switch it off? Hand it over to ITU control? :-)
>=20
> The Internet was designed from the outset to work around breakage. =
Packet
> fragmentation issues will always be with us unfortunately. The =
networks which
> have these problems will fix them: Darwinism will take care of that =
eventually.
> Until then everyone else just has to work around them or ignore their
> brokenness. 'coz that's how it works.
>=20
> We (for some definition of we) might come up with some tools to help =
identify
> the problem or do some outreach and education to help mend these =
broken
> networks. However I am sceptical those sort of things will be =
successful. After
> all we still have nets, servers and middleboxes that can't/won't =
handle EDNS
> correctly or assume that DNS packets only ever go over UDP and are =
always <
> 512 bytes.




From nobody Thu Sep 21 05:20:28 2017
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C75132055 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 05:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 o7dWNJfqo4qs for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 05:20:25 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D67E612EC30 for <dnsop@ietf.org>; Thu, 21 Sep 2017 05:20:24 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id F08C96A401; Thu, 21 Sep 2017 14:20:22 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id 34F2C6A3FC; Thu, 21 Sep 2017 14:20:17 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59c3ae81-034f-7f000001272a-7f000001c926-1 for <multiple-recipients>; Thu, 21 Sep 2017 14:20:17 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id 9D0EB6A3A6; Thu, 21 Sep 2017 14:20:16 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id 919773C19F4; Thu, 21 Sep 2017 14:20:16 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBPIgLYM9orW; Thu, 21 Sep 2017 14:20:16 +0200 (CEST)
Received: from [10.242.2.24] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 754333C19EE; Thu, 21 Sep 2017 14:20:16 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Thu, 21 Sep 2017 14:20:15 +0200
Message-ID: <8FD138C0-3D99-42E6-8EB2-97C5FA2F0C80@powerdns.com>
In-Reply-To: <20170921034533.d2isi2idl7cyepea@mx4.yitter.info>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
X-Mailer: MailMate (1.9.7r5418)
Content-Transfer-Encoding: quoted-printable
X-purgate-ID: 151428::1505996417-0000034F-1B5E1D16/0/0
X-purgate-type: clean
X-purgate-size: 2918
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8ysS8D1NXYLNPNBPNp--c2irmZM>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 12:20:26 -0000

Hello Andrew,

thank you for this, I like it a lot. One nit below.

On 21 Sep 2017, at 5:45, Andrew Sullivan wrote:

>       [RFC2308], however, has an alternate definition that puts the
>       QNAME in the answer (or series of answers) instead of the query.
>       It defines QNAME as: "...the name in the query section of an
>       answer, or where this resolves to a CNAME, or CNAME chain, the
>       data field of the last CNAME.  The last CNAME in this sense is
>       that which contains a value which does not resolve to another
>       CNAME."  This definition has a certain internal logic, because of
>       the way CNAME substitution works and the definition of CNAME.  If
>       a name server does not find an RRset that matches a query, but it
>       finds the same name in the same class with a CNAME record, then
>       the name server "includes the CNAME record in the response and
>       restarts the query at the domain name specified in the data field
>       of the CNAME record."  ([RFC1034] Section 3.6.2).  This is made
>       explicit in the resolution algorithm outlined in Section 4.3.2,

It=E2=80=99s unclear that 4.3.2 is in 1034, as 1034 is in parens just bef=
ore.

>       which says to "change QNAME to the canonical name in the CNAME RR=
,
>       and go back to step 1" in the case of a CNAME RR.  Since a CNAME
>       record explicitly declares that the owner name is canonically
>       named what is in the RDATA, then there is a way to view the new
>       name (i.e. the name that was in the RDATA of the CNAME RR) as als=
o
>       being the QNAME.
>
>       This creates a kind of confusion, however, because the answer to =
a
>       query that results in CNAME processing contains in the echoed
>       Question Section one QNAME (the name in the original query), and =
a
>       second QNAME that is in the data field of the last CNAME.  The
>       confusion comes from the iterative/recursive mode of resolution,
>       which finally returns an answer that need not actually have the
>       same owner name as the QNAME contained in the original query.
>
>       To address this potential confusion, it is helpful to distinguish
>       between two meanings:
>
>       QNAME (original)  The name actually sent in the Question
>          Section in the orignal query, which is always echoed in the
>          (final) reply in the Question Section when the QR bit is set t=
o
>          1.
>
>       QNAME (effective)  The name actually resolved, which is either th=
e
>          name actually queried or else the last name in a CNAME chain a=
s
>          defined in [RFC2308].
>
> I'm certainly not wedded to these two names.

They certainly are adequate, and I do not have better suggestions.

Wonderful work!

Kind regards,
--=20
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Thu Sep 21 05:52:49 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 000B613305E for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 05:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=kAhWopvZ; dkim=pass (1024-bit key) header.d=yitter.info header.b=URdGGWpH
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 445CXMtNfS44 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 05:52:46 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF10132351 for <dnsop@ietf.org>; Thu, 21 Sep 2017 05:52:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 678A8BEDA1 for <dnsop@ietf.org>; Thu, 21 Sep 2017 12:52:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1505998365; bh=fRfcQtpfAIfoGeRv8Nr2UQXT48I32pJ0AYJ7w5MNp3c=; h=Date:From:To:Subject:References:In-Reply-To:From; b=kAhWopvZH0/7qEpQpYVNw8BCs+Oa2qmcyk5/gCR0bL7R4T29+FeJD72CCQyfDn9W6 lxrHOFmKVZhUSNZmjUDg10Hs1WIUg5XoJCCgmuykgHO/8nCyRIi6VclrabcuY0E4Ar gC2zXG2a956d2bKVLc5mclwUMqj80XvfkPrBRiN4=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G_CIWa6s39WH for <dnsop@ietf.org>; Thu, 21 Sep 2017 12:52:43 +0000 (UTC)
Date: Thu, 21 Sep 2017 08:52:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1505998363; bh=fRfcQtpfAIfoGeRv8Nr2UQXT48I32pJ0AYJ7w5MNp3c=; h=Date:From:To:Subject:References:In-Reply-To:From; b=URdGGWpHrmAMyjBQy+F56CE//Vejgbn2M9DYjKYx5w0zIXloN6WftRB2U66wsAdOG 0oF4+PcZ91iFdROX7j57cFF/ERPjJyh2HAO6oCCeZqO0S/4Ba+WgdGz90PHUpOBFZ3 gA2bXz3fxgTIRAJUXMNw+Y1/SqLf8rKnhPhWVSc0=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170921125242.73apv3b434zmejzb@mx4.yitter.info>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <59C34510.4080705@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rS_0Dv52adN4DrNWX1tJiXIGzjA>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiBGd2Q6IEktRCBBY3Rpb246IGRyYWZ0LXNv?= =?utf-8?q?ng-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 12:52:48 -0000

Hi,

On Wed, Sep 20, 2017 at 09:50:24PM -0700, Paul Vixie wrote:
> 
>  what we have to do is arrange to fragment, using the
> ipv6 extension header, all ipv6 udp, for a period of not less than five
> years. noone who blocks ipv6 extension headers should be able to get
> reliable ipv6 udp services. we have to make this problem felt where it is
> made. we must NOT work around it to insulate the makers of the problem from
> the costs of their actions.

I think that the above suggestion needs to define carefully who "we"
is in each sentence.  Because I am very far from convinced that the
"we" in each case is the same people, and also very far from convinced
that we are going to be able to "make" this happen, given our lack of
protocol police.  Operators have one incentive, which is to make their
customers stop calling; if our plan is to make IPv6 even less reliable
than it has been historically, I think the operators are going to point
us to the nearest short pier and tell us to take a long walk.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu Sep 21 06:12:48 2017
Return-Path: <shuque@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7937B1347DC for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DanOe86I2u3q for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:12:46 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2093113305F for <dnsop@ietf.org>; Thu, 21 Sep 2017 06:12:46 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id c19so3027869vke.11 for <dnsop@ietf.org>; Thu, 21 Sep 2017 06:12:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IpegKpFuL3u+JhpBSOyBqTVQHPtoBDVnKzoLQ7zWWww=; b=laVbxjnBeMbD+8yNDXhyc8+fIcEln0OxxBnty5BqJVjePDoHnF7IOiteNAR/irl75c Ic5N9C3HGiJcSPCD5TLP7FkdRa2ddvpU2IJ8YmTBBmJJLXY361GSZKQcNYqHApkwqdy3 4GsIP8N6MPb4Q38EnSmJyTcedkepkc8snlkKRl4Kz/lRBTOiT2hjIlVT8yYI0mwxfKRQ 8m9HMFFGyH20xJSIQinumfoWv+KUqKiL1XuuMpt5/f0mBPgDmGGCCpSi1cxyzjnUQLhv a8pHuzhBEu2gVsYxXUSxsdDrpV8PzOPb7SMbJRcdLgbejhwTz6Pq0+z5B3yBFJtX2sbZ HOnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IpegKpFuL3u+JhpBSOyBqTVQHPtoBDVnKzoLQ7zWWww=; b=jvgM2bCALJPsc/UVp8PrukEk9d4n8Dn53HOwNiG9tUFMg3lzDgOPMpwpj3clxsiGPH 2/JyyGFBlN4y4/6E5LqTkTyw3sA35DLQbSHtg0PWh0bN0wWqWu9NVPZwN9T4Heo+8MgX eewFe8jDwdK1tS41FJO4/kr7gRf/uVAkQJZE4TYBDRLA5kXaH4VGJ49695p5zPc4UO2t pFdBG8mtQfTFgLOGxOEAALJBZH38jIAF5bBqqsK+tJd27OcuYbCHo6rR9t/0f4IGc6X4 nyS3qtiqDfr6dxFkb1kOsI975He01utZOdDpeeAPtvoDKA2Xc2gL6fVrlQwse2Zigs82 lXiA==
X-Gm-Message-State: AHPjjUgd5wl3Kba/ppyZ+s8EssH3eB2AZjOHzNbl3uroJI45iTkr33Yp sHRismtK1EC8Jez0EXP4rcna1tLGDF/JMyIyueo=
X-Google-Smtp-Source: AOwi7QB6RkePtrI4Hn49GD7C/NzT9QrBKkzjrDU5JUzPJZdB9JJCnTP5IjUhgXn+IClceoNnDrTBqlT1wSSlgxlZDyQ=
X-Received: by 10.31.16.232 with SMTP id 101mr1743082vkq.158.1505999565176; Thu, 21 Sep 2017 06:12:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.54.41 with HTTP; Thu, 21 Sep 2017 06:12:44 -0700 (PDT)
In-Reply-To: <20170921034533.d2isi2idl7cyepea@mx4.yitter.info>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info>
From: Shumon Huque <shuque@gmail.com>
Date: Thu, 21 Sep 2017 09:12:44 -0400
Message-ID: <CAHPuVdVc39kGZc1Kd-RsN=McWmoKLA5=AQPCJbCVkYxhTAAo6g@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114365c41d476e0559b2d91a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Kl3T4k3zM2ev3fFGYA-qBIAOSiY>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 13:12:47 -0000

--001a114365c41d476e0559b2d91a
Content-Type: text/plain; charset="UTF-8"

On Wed, Sep 20, 2017 at 11:45 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

>
>       To address this potential confusion, it is helpful to distinguish
>       between two meanings:
>
>       QNAME (original)  The name actually sent in the Question
>          Section in the orignal query, which is always echoed in the
>          (final) reply in the Question Section when the QR bit is set to
>          1.
>
>       QNAME (effective)  The name actually resolved, which is either the
>          name actually queried or else the last name in a CNAME chain as
>          defined in [RFC2308].
>
> I'm certainly not wedded to these two names.
>


These two terms sound reasonable to me.

-- 
Shumon Huque

--001a114365c41d476e0559b2d91a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Sep 20, 2017 at 11:45 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
=C2=A0 =C2=A0 =C2=A0 To address this potential confusion, it is helpful to =
distinguish<br>
=C2=A0 =C2=A0 =C2=A0 between two meanings:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 QNAME (original)=C2=A0 The name actually sent in the Q=
uestion<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Section in the orignal query, which is al=
ways echoed in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(final) reply in the Question Section whe=
n the QR bit is set to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 QNAME (effective)=C2=A0 The name actually resolved, wh=
ich is either the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0name actually queried or else the last na=
me in a CNAME chain as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0defined in [RFC2308].<br>
<br>
I&#39;m certainly not wedded to these two names.<br></blockquote><div><br><=
/div><div><br></div><div>These two terms sound reasonable to me.</div><div>=
<br></div><div>--=C2=A0</div><div>Shumon Huque</div><div><br></div></div></=
div></div>

--001a114365c41d476e0559b2d91a--


From nobody Thu Sep 21 06:17:18 2017
Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62F2B1347DC for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 1IA2-3-7mOJO for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:17:14 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FBFC134B45 for <dnsop@ietf.org>; Thu, 21 Sep 2017 06:17:14 -0700 (PDT)
Received: from [10.20.1.7] (fb1.lds3.event.aql.com [141.170.18.58]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 70D852421249; Thu, 21 Sep 2017 13:17:12 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CAHPuVdVc39kGZc1Kd-RsN=McWmoKLA5=AQPCJbCVkYxhTAAo6g@mail.gmail.com>
Date: Thu, 21 Sep 2017 14:17:11 +0100
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <799422B9-F267-4227-8895-7620AAFDB901@rfc1035.com>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info> <CAHPuVdVc39kGZc1Kd-RsN=McWmoKLA5=AQPCJbCVkYxhTAAo6g@mail.gmail.com>
To: Shumon Huque <shuque@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/NSfGUqgPJk2KVMOUj4GDhp5GB5k>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 13:17:17 -0000

> On 21 Sep 2017, at 14:12, Shumon Huque <shuque@gmail.com> wrote:
>=20
> On Wed, Sep 20, 2017 at 11:45 PM, Andrew Sullivan =
<ajs@anvilwalrusden.com> wrote:
>=20
>       To address this potential confusion, it is helpful to =
distinguish
>       between two meanings:
>=20
>       QNAME (original)  The name actually sent in the Question
>          Section in the orignal query, which is always echoed in the
>          (final) reply in the Question Section when the QR bit is set =
to
>          1.
>=20
>       QNAME (effective)  The name actually resolved, which is either =
the
>          name actually queried or else the last name in a CNAME chain =
as
>          defined in [RFC2308].

Maybe the definition of QNAME (effective) needs to be extended to =
include the result of NAPTR record processing? Says he running away =
quickly...


From nobody Thu Sep 21 06:31:16 2017
Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FED3134AA7 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 m6TbfuHukjlk for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 06:31:13 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C01021320CF for <dnsop@ietf.org>; Thu, 21 Sep 2017 06:31:13 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:33108) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dv1ZO-000Fu7-1k (Exim 4.89) (return-path <dot@dotat.at>); Thu, 21 Sep 2017 14:31:10 +0100
Date: Thu, 21 Sep 2017 14:31:10 +0100
From: Tony Finch <dot@dotat.at>
To: Jim Reid <jim@rfc1035.com>
cc: Shumon Huque <shuque@gmail.com>, dnsop WG <dnsop@ietf.org>,  Andrew Sullivan <ajs@anvilwalrusden.com>
In-Reply-To: <799422B9-F267-4227-8895-7620AAFDB901@rfc1035.com>
Message-ID: <alpine.DEB.2.11.1709211430040.2486@grey.csi.cam.ac.uk>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info> <CAHPuVdVc39kGZc1Kd-RsN=McWmoKLA5=AQPCJbCVkYxhTAAo6g@mail.gmail.com> <799422B9-F267-4227-8895-7620AAFDB901@rfc1035.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4q27wjlHtd4Ov8cYtAsHvgwiNBA>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 13:31:15 -0000

Jim Reid <jim@rfc1035.com> wrote:
>
> Maybe the definition of QNAME (effective) needs to be extended to
> include the result of NAPTR record processing? Says he running away
> quickly...

As I understand it, NAPTR processing happens in applications outside the
DNS so the result is a QNAME (original) from the DNS point of view.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Southeast Iceland: Southeasterly 5 or 6. Moderate. Showers. Good.


From nobody Thu Sep 21 09:01:54 2017
Return-Path: <each@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E515132D53 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 09:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 BbyPcem5726P for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 09:01:50 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A4F132125 for <dnsop@ietf.org>; Thu, 21 Sep 2017 09:01:50 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 028CA34BD26; Thu, 21 Sep 2017 16:01:16 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id E6F97216C1E; Thu, 21 Sep 2017 16:01:15 +0000 (UTC)
Date: Thu, 21 Sep 2017 16:01:15 +0000
From: Evan Hunt <each@isc.org>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
Cc: dnsop@ietf.org
Message-ID: <20170921160115.GA20526@isc.org>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info> <8FD138C0-3D99-42E6-8EB2-97C5FA2F0C80@powerdns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8FD138C0-3D99-42E6-8EB2-97C5FA2F0C80@powerdns.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/UNV7ZClO8nrwx9uAaK5iyl5Mv3Q>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 16:01:52 -0000

On Thu, Sep 21, 2017 at 02:20:15PM +0200, Peter van Dijk wrote:
> thank you for this, I like it a lot. One nit below.

Me too, with another nit...

> >       This creates a kind of confusion, however, because the answer to a
> >       query that results in CNAME processing contains in the echoed
> >       Question Section one QNAME (the name in the original query), and a
> >       second QNAME that is in the data field of the last CNAME.  The

Why only the "last CNAME?" If a chain contains more than one CNAME, the
answer includes intermediate names as well:

;; ANSWER SECTION:
www.paypal.com.         5       IN      CNAME   geo.paypal.com.akadns.net.
geo.paypal.com.akadns.net. 5    IN      CNAME   wlb.paypal.com.akadns.net.
wlb.paypal.com.akadns.net. 5    IN      CNAME   www.paypal.com.edgekey.net.
www.paypal.com.edgekey.NET. 5   IN      CNAME   e3694.a.akamaiedge.net.
e3694.a.akamaiedge.net. 5       IN      A       104.91.181.63

> >       QNAME (effective)  The name actually resolved, which is either the
> >          name actually queried or else the last name in a CNAME chain as
> >          defined in [RFC2308].

This does match the use of the term in RFC 2308, but in other contexts,
I think it would be better to expand it to include intermediate names:
"A name actually resolved, which is either the name originally queried,
or a name received in a CNAME chain response." 

RFC 2308 is interested in caching of answers after recursion is done,
but if one were discussing the recursion process itself, this would be a
natural term to use for itermediate names.  ("If the response is a CNAME,
update the effective QNAME to the CNAME target and go back to step 2...")

If it's necessary to have a specific term that only refers to the *last*
name, perhaps "QNAME (final)" would be a better choice for that.

Incidentally "CNAME chain as defined in [RFC2308]" is ambiguous. RFC
2308 has a definition of QNAME that includes the last CNAME in a chain,
but it does not define the term "CNAME chain".

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.


From nobody Thu Sep 21 10:26:51 2017
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85977126E64 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 10:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 3Jn_gDVA6LEe for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 10:26:48 -0700 (PDT)
Received: from mx2.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5009B126C0F for <dnsop@ietf.org>; Thu, 21 Sep 2017 10:26:48 -0700 (PDT)
Received: by mx2.open-xchange.com (Postfix, from userid 1001) id 62EE36A3A6; Thu, 21 Sep 2017 19:26:46 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.open-xchange.com (Postfix) with ESMTP id 24FCA6A33A; Thu, 21 Sep 2017 19:26:39 +0200 (CEST)
Received: from [127.0.0.1] (helo=mx2.open-xchange.com) by localhost with ESMTP (eXpurgate 4.1.8) (envelope-from <peter.van.dijk@powerdns.com>) id 59c3f64e-034f-7f000001272a-7f000001a71d-1 for <multiple-recipients>; Thu, 21 Sep 2017 19:26:38 +0200
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.open-xchange.com (Postfix) with ESMTPS id C52486A330; Thu, 21 Sep 2017 19:26:38 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by open-xchange.com (Postfix) with ESMTP id B76283C19DF; Thu, 21 Sep 2017 19:26:38 +0200 (CEST)
Received: from open-xchange.com ([127.0.0.1]) by localhost (imap.open-xchange.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51m5A1MTkaHM; Thu, 21 Sep 2017 19:26:38 +0200 (CEST)
Received: from [10.242.2.24] (095-096-086-198.static.chello.nl [95.96.86.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 9A4C43C0ACA; Thu, 21 Sep 2017 19:26:38 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop@ietf.org
Date: Thu, 21 Sep 2017 19:26:37 +0200
Message-ID: <5D87C9A8-1B89-4EA2-BC6D-09B4AFDE0111@powerdns.com>
In-Reply-To: <20170921160115.GA20526@isc.org>
References: <149894524329.526.18431408698564464455@ietfa.amsl.com> <20170824142147.lshdlmjv62nojd32@nic.fr> <20170921034533.d2isi2idl7cyepea@mx4.yitter.info> <8FD138C0-3D99-42E6-8EB2-97C5FA2F0C80@powerdns.com> <20170921160115.GA20526@isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.7r5418)
Content-Transfer-Encoding: quoted-printable
X-purgate-ID: 151428::1506014799-0000034F-074720EE/0/0
X-purgate-type: clean
X-purgate-size: 1972
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pdbmwjryV41dHamJsySENX8_2ZI>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 17:26:51 -0000

Hello,

On 21 Sep 2017, at 18:01, Evan Hunt wrote:

> On Thu, Sep 21, 2017 at 02:20:15PM +0200, Peter van Dijk wrote:
>> thank you for this, I like it a lot. One nit below.
>
> Me too, with another nit...
>
>>>       This creates a kind of confusion, however, because the answer=20
>>> to a
>>>       query that results in CNAME processing contains in the echoed
>>>       Question Section one QNAME (the name in the original query),=20
>>> and a
>>>       second QNAME that is in the data field of the last CNAME.  The
>
> Why only the "last CNAME?" If a chain contains more than one CNAME,=20
> the
> answer includes intermediate names as well:
>
> ;; ANSWER SECTION:
> www.paypal.com.         5       IN      CNAME  =20
> geo.paypal.com.akadns.net.
> geo.paypal.com.akadns.net. 5    IN      CNAME  =20
> wlb.paypal.com.akadns.net.
> wlb.paypal.com.akadns.net. 5    IN      CNAME  =20
> www.paypal.com.edgekey.net.
> www.paypal.com.edgekey.NET. 5   IN      CNAME  =20
> e3694.a.akamaiedge.net.
> e3694.a.akamaiedge.net. 5       IN      A       104.91.181.63

That=E2=80=99s a very good point. If any of these CNAMEs are synthesised =
from=20
wildcards, and DNSSEC is in play, then the use of QNAME in RFC5155 (and=20
presumably also the NSEC equivalent) demands that each step of this=20
chain is the QNAME at some point.

> If it's necessary to have a specific term that only refers to the=20
> *last*
> name, perhaps "QNAME (final)" would be a better choice for that.

+1 - with the caveat that the definition needs to decide if it applies=20
when the chain does not end (a loop, or a failure). Is that =E2=80=98fina=
l=E2=80=99?=20
=E2=80=98effective=E2=80=99?=E2=80=99 =E2=80=98intermediate=E2=80=99? Per=
haps the right division is=20
original+intermediate+final, dropping effective in favour of the=20
intermediate+final division.

Kind regards,
--=20
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/


From nobody Thu Sep 21 19:31:33 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D812F13339D for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 19:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 pFgS-9Q8fPo8 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 19:31:30 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27429132076 for <dnsop@ietf.org>; Thu, 21 Sep 2017 19:31:30 -0700 (PDT)
Received: from [10.0.0.23] (pool-173-79-98-3.washdc.fios.verizon.net [173.79.98.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 406B261FA2; Fri, 22 Sep 2017 02:31:29 +0000 (UTC)
Message-ID: <59C47601.5030804@redbarn.org>
Date: Thu, 21 Sep 2017 19:31:29 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>
CC: 'dnsop' <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6
In-Reply-To: <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3p31uO89FtbLHEGOdDuptAzeZYU>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 02:31:32 -0000

Davey Song(宋林健) wrote:
> Hi Paul,
>
> I know you suggest expose the problem and let the trouble maker
> feeling the pain themselves. But return to the specific issue, from
> APNIC's measurement the ASes in the path are dropping the fragments,
> rather than end ASes. From these ASes' view , it's your pain not
> theirs.

it's a question of first mover advantage. EDNS will never be fully 
deployed, because of the middleboxes built before 1999 who "know" what a 
UDP/53 datagram has to look like, and which disallow ADCOUNT>0 && QR=0.

we can, if we wish, continue to standardize one protocol, watch as the 
world deploys a different one, and still pretent that our effort was 
worthwhile. however, this would fit the technical definition of 
"insanity", and i urge that we avoid this course of action.

> In another word, we are facing the fragmented and uncooperative
> Internet. What should we do ? It is very hard to coordinate all parts
> and networks. DNS is a field with lots of tussle.

we need a kernel option for various open source operating systems which 
causes all UDP to be fragmented at 512 octets of payload. for ipv4, so 
that we can hard-smash every middlebox which still prevents EDNS from 
being deployed, and for ipv6 also, so that we can hard-smash any middle 
or edge network who won't carry ipv6 extension headers.

and we need to turn this on everywhere. root, gtld, cctld, recursives, 
authoriatives, 8.8.8.8, opendns... Everywhere. with a press release to 
pre-announce the flag day.

if we're not going to stand up for the standards we write, then we 
should admit that nothing except tcp/80 will work, and avoid all else.

-- 
P Vixie


From nobody Thu Sep 21 20:14:38 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9AFC128D0D for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 20:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 pW_jHhKrcVkR for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 20:14:35 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 614141252BA for <dnsop@ietf.org>; Thu, 21 Sep 2017 20:14:35 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 603513495A8; Fri, 22 Sep 2017 03:14:02 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 408D116003D; Fri, 22 Sep 2017 03:14:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0F0F1160069; Fri, 22 Sep 2017 03:14:02 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id z3B-fx-km0ql; Fri, 22 Sep 2017 03:14:01 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 78DDB16003D; Fri, 22 Sep 2017 03:14:00 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 94ABB87A157F; Fri, 22 Sep 2017 13:13:58 +1000 (AEST)
To: Paul Vixie <paul@redbarn.org>
Cc: =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>, 'dnsop' <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6 <59C47601.5030804@redbarn.org>
In-reply-to: Your message of "Thu, 21 Sep 2017 19:31:29 -0700." <59C47601.5030804@redbarn.org>
Date: Fri, 22 Sep 2017 13:13:58 +1000
Message-Id: <20170922031358.94ABB87A157F@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pNRw48ksvsjcB38DY2ln7mEmPJY>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 03:14:37 -0000

In message <59C47601.5030804@redbarn.org>, Paul Vixie writes:
> Davey Song() wrote:
> > Hi Paul,
> >
> > I know you suggest expose the problem and let the trouble maker
> > feeling the pain themselves. But return to the specific issue, from
> > APNIC's measurement the ASes in the path are dropping the fragments,
> > rather than end ASes. From these ASes' view , it's your pain not
> > theirs.
>
> it's a question of first mover advantage. EDNS will never be fully
> deployed, because of the middleboxes built before 1999 who "know" what a
> UDP/53 datagram has to look like, and which disallow ADCOUNT>0 && QR=0.

The ones built after 1999 that assume EDNS will always have a version
field of zero, or that there won't be any EDNS options, or that
there won't be any EDNS flags bits, other than DO, are the biggest
problem.

> we can, if we wish, continue to standardize one protocol, watch as the
> world deploys a different one, and still pretent that our effort was
> worthwhile. however, this would fit the technical definition of
> "insanity", and i urge that we avoid this course of action.
>
> > In another word, we are facing the fragmented and uncooperative
> > Internet. What should we do ? It is very hard to coordinate all parts
> > and networks. DNS is a field with lots of tussle.
>
> we need a kernel option for various open source operating systems which
> causes all UDP to be fragmented at 512 octets of payload. for ipv4, so
> that we can hard-smash every middlebox which still prevents EDNS from
> being deployed, and for ipv6 also, so that we can hard-smash any middle
> or edge network who won't carry ipv6 extension headers.
>
> and we need to turn this on everywhere. root, gtld, cctld, recursives,
> authoriatives, 8.8.8.8, opendns... Everywhere. with a press release to
> pre-announce the flag day.
>
> if we're not going to stand up for the standards we write, then we
> should admit that nothing except tcp/80 will work, and avoid all else.

Just padding UDP responses to EDNS buffer size should be enough to
force fragmentation.  If you advertise a 4096 buffer you should be
able to accept such a response.

We also need to bump the EDNS version number.  Going to EDNS(1)
will hit the firewalls that think EDNS(0) is the only EDNS version
they will ever see.

BIND 9.11 is already adding a DNS COOKIE option to every request.
That is causing some firewalls to be fixed as well as some nameservers.
We haven't added additional workaround code for this.

Mark
> --
> P Vixie
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep 21 20:41:16 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC3E21321D8 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 20:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 splMrZNJdUcE for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 20:41:13 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF2731321AC for <dnsop@ietf.org>; Thu, 21 Sep 2017 20:41:13 -0700 (PDT)
Received: from [10.0.0.23] (pool-173-79-98-3.washdc.fios.verizon.net [173.79.98.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id A574861FA2; Fri, 22 Sep 2017 03:41:12 +0000 (UTC)
Message-ID: <59C48658.9000608@redbarn.org>
Date: Thu, 21 Sep 2017 20:41:12 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.19 (Windows/20170908)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
CC: =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>,  'dnsop' <dnsop@ietf.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6 <59C47601.5030804@redbarn.org> <20170922031358.94ABB87A157F@rock.dv.isc.org>
In-Reply-To: <20170922031358.94ABB87A157F@rock.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/y2rrrGWfybZP3GRlpY4RxWi1Zac>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 03:41:15 -0000

Mark Andrews wrote:
...
> Just padding UDP responses to EDNS buffer size should be enough to
> force fragmentation.  If you advertise a 4096 buffer you should be
> able to accept such a response.

i don't want to waste the octets. a lot of links are still mobile. 
forcing source fragmentation for payloads longer than 512 will do.

> We also need to bump the EDNS version number.  Going to EDNS(1)
> will hit the firewalls that think EDNS(0) is the only EDNS version
> they will ever see.

that would drag in version negotiation -- a lot of responders would say 
BADVERS which would lead, best case, to another round trip. but since 
the version negotiation code paths aren't tested, it may be worse.

> BIND 9.11 is already adding a DNS COOKIE option to every request.
> That is causing some firewalls to be fixed as well as some nameservers.
> We haven't added additional workaround code for this.

nice. thanks for that.

-- 
P Vixie


From nobody Thu Sep 21 21:25:28 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16632132CE7 for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 21:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 dccEx16a5RDn for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 21:25:25 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C46DE1321DF for <dnsop@ietf.org>; Thu, 21 Sep 2017 21:25:25 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id DF41B34B423; Fri, 22 Sep 2017 04:24:55 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id BE49E16003D; Fri, 22 Sep 2017 04:24:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3EC08160069; Fri, 22 Sep 2017 04:24:55 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mZpQWasoyTGH; Fri, 22 Sep 2017 04:24:55 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id C639816003D; Fri, 22 Sep 2017 04:24:54 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 08EA187A1E04; Fri, 22 Sep 2017 14:24:53 +1000 (AEST)
To: Paul Vixie <paul@redbarn.org>
Cc: =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>, 'dnsop' <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6 <59C47601.5030804@redbarn.org> <20170922031358.94ABB87A157F@rock.dv.isc.org> <59C48658.9000608@redbarn.org>
In-reply-to: Your message of "Thu, 21 Sep 2017 20:41:12 -0700." <59C48658.9000608@redbarn.org>
Date: Fri, 22 Sep 2017 14:24:52 +1000
Message-Id: <20170922042453.08EA187A1E04@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/V1CWe6Zpvxddl8aqOIoR9HjzRSk>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 04:25:28 -0000

In message <59C48658.9000608@redbarn.org>, Paul Vixie writes:
> Mark Andrews wrote:
> ...
> > Just padding UDP responses to EDNS buffer size should be enough to
> > force fragmentation.  If you advertise a 4096 buffer you should be
> > able to accept such a response.
> 
> i don't want to waste the octets. a lot of links are still mobile. 
> forcing source fragmentation for payloads longer than 512 will do.

Setsockopt IPV6_USE_MIN_MTU=1 for IPv6.
 
> > We also need to bump the EDNS version number.  Going to EDNS(1)
> > will hit the firewalls that think EDNS(0) is the only EDNS version
> > they will ever see.
> 
> that would drag in version negotiation -- a lot of responders would say 
> BADVERS which would lead, best case, to another round trip. but since 
> the version negotiation code paths aren't tested, it may be worse.

Version negotiation occuring will self correct.  A extra round trip
isn't too expensive.  We get enough FORMERR/BADVERS to EDNS(0) +
DNS COOKIE queries to know that it isn't a practical issue.

I've tested enough version negotiation paths.  See https://ednscomp.isc.org/
The entries with "badversion" show a failed EDNS version negotiation.
The entire Alexa top 1M is scanned once a month.

	EDNS(0) + rcode != BADVERS -> badversion
	BADVERS + response version >= request version -> badversion

> > BIND 9.11 is already adding a DNS COOKIE option to every request.
> > That is causing some firewalls to be fixed as well as some nameservers.
> > We haven't added additional workaround code for this.
> 
> nice. thanks for that.
> 
> -- 
> P Vixie
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Sep 21 22:04:50 2017
Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C00513339D for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 22:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.88
X-Spam-Level: 
X-Spam-Status: No, score=-5.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 lRsvMj0WQxNN for <dnsop@ietfa.amsl.com>; Thu, 21 Sep 2017 22:04:47 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35FF71331B0 for <dnsop@ietf.org>; Thu, 21 Sep 2017 22:04:47 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id EF60234B78C; Fri, 22 Sep 2017 05:04:44 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D75F716003D; Fri, 22 Sep 2017 05:04:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A3A4D160074; Fri, 22 Sep 2017 05:04:44 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BvzWBz6aKRtu; Fri, 22 Sep 2017 05:04:44 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 5A03B16003D; Fri, 22 Sep 2017 05:04:44 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 1290487A2DC3; Fri, 22 Sep 2017 15:04:42 +1000 (AEST)
Cc: Paul Vixie <paul@redbarn.org>, =?UTF-8?B?IkRhdmV5IFNvbmco5a6L5p6X5YGlKSI=?= <ljsong@biigroup.cn>, 'dnsop' <dnsop@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn>+5DE3FF4CB4E4721A <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn>+1004318D79D4A4F6 <59C47601.5030804@redbarn.org> <20170922031358.94ABB87A157F@rock.dv.isc.org> <59C48658.9000608@redbarn.org> <20170922042453.08EA187A1E04@rock.dv.isc.org>
In-reply-to: Your message of "Fri, 22 Sep 2017 14:24:52 +1000." <20170922042453.08EA187A1E04@rock.dv.isc.org>
Date: Fri, 22 Sep 2017 15:04:41 +1000
Message-Id: <20170922050442.1290487A2DC3@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8ECD3zBSyBxpL6WV0eqF7gn-A2E>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 05:04:49 -0000

In message <20170922042453.08EA187A1E04@rock.dv.isc.org>, Mark Andrews writes:

> I've tested enough version negotiation paths.  See https://ednscomp.isc.org/
> The entries with "badversion" show a failed EDNS version negotiation.
> The entire Alexa top 1M is scanned once a month.

I've added a link to the raw data for those that want to investigate further.
 
> 	EDNS(0) + rcode != BADVERS -> badversion
> 	BADVERS + response version >= request version -> badversion
> 
> > > BIND 9.11 is already adding a DNS COOKIE option to every request.
> > > That is causing some firewalls to be fixed as well as some nameservers.
> > > We haven't added additional workaround code for this.
> > 
> > nice. thanks for that.
> > 
> > -- 
> > P Vixie
> > 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Sep 22 06:58:47 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 691BA134458 for <dnsop@ietfa.amsl.com>; Fri, 22 Sep 2017 06:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=dznMzn1R; dkim=pass (1024-bit key) header.d=yitter.info header.b=Fa0UYMbl
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 XHbC-hU-h4eJ for <dnsop@ietfa.amsl.com>; Fri, 22 Sep 2017 06:58:45 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14A1A134456 for <dnsop@ietf.org>; Fri, 22 Sep 2017 06:58:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 562F3BEDA1 for <dnsop@ietf.org>; Fri, 22 Sep 2017 13:58:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1506088724; bh=uEjPb1ijeSxSRQKDL8TgAaicsN11CTJegkPko6k35P4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=dznMzn1REcM6KAKPGZYNJ/GGraXpVBOo73v0BlgyMGNCFUDpcIig1QXPxfOxN84+6 SGOmFmCJ/VHk+5MJ5uXSF4KkWCBHGOjf3DBLWYMsH0JB3GLXSNahblpD5jUCSTQ2CI WRZW3Yv9+qBrJuLQMjI7pbcsBUzYeY0MnFUmCTMg=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvmJbBXKOr8D for <dnsop@ietf.org>; Fri, 22 Sep 2017 13:58:42 +0000 (UTC)
Date: Fri, 22 Sep 2017 09:58:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1506088722; bh=uEjPb1ijeSxSRQKDL8TgAaicsN11CTJegkPko6k35P4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Fa0UYMblvdtemoWHKQfPdvKnp2c9b4o3/aZkRxC3Nv83tnRjrr7p4KGkveKRi5KBk r4Fi8K5nYK9/DMH+wzf8puJ+dfAh0bugxva7DRfv9ok66ByzKNAfoRaMj7oKaW+4nM j9JS+3Xo36QiSPIxmfgEaAmG6As3fu3vmvnBtqcc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170922135842.5wy4fjrzy6zhgahz@mx4.yitter.info>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn> <59C47601.5030804@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <59C47601.5030804@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mpEy0uZelR6bw0JWXz4povbyIYI>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 13:58:46 -0000

On Thu, Sep 21, 2017 at 07:31:29PM -0700, Paul Vixie wrote:
> we can, if we wish, continue to standardize one protocol, watch as the world
> deploys a different one, and still pretent that our effort was worthwhile.
> however, this would fit the technical definition of "insanity", and i urge
> that we avoid this course of action.

[…]

> we need a kernel option for various open source operating systems which
> causes all UDP to be fragmented at 512 octets of payload.

If working on a protocol that merely depends on certain middleboxes
eventually die is "insanity", what do we call it when people work on a
protocol that depends on UDP fragments working everywhere?

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Sep 22 08:43:51 2017
Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE791344DA for <dnsop@ietfa.amsl.com>; Fri, 22 Sep 2017 08:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 TYvL_6VYajLC for <dnsop@ietfa.amsl.com>; Fri, 22 Sep 2017 08:43:48 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5ADA1344E3 for <dnsop@ietf.org>; Fri, 22 Sep 2017 08:43:48 -0700 (PDT)
Received: from [172.20.175.126] (unknown [65.201.185.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 25EA461FA2; Fri, 22 Sep 2017 15:43:47 +0000 (UTC)
Date: Fri, 22 Sep 2017 15:43:43 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <20170922135842.5wy4fjrzy6zhgahz@mx4.yitter.info>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn> <59C47601.5030804@redbarn.org> <20170922135842.5wy4fjrzy6zhgahz@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: dnsop@ietf.org,Andrew Sullivan <ajs@anvilwalrusden.com>
From: P Vix <paul@redbarn.org>
Message-ID: <19261992-0847-47C4-AAD8-46FB85BF21C8@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Xvy9QwODfOSl05rmOMu8vtc2jik>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgIOetlOWkjTogIEZ3ZDogSS1EIEFjdGlv?= =?utf-8?q?n=3A_draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 15:43:50 -0000

On September 22, 2017 9:58:42 AM EDT, Andrew Sullivan <ajs@anvilwalrusden=
=2Ecom> wrote:
>On Thu, Sep 21, 2017 at 07:31:29PM -0700, Paul Vixie wrote:
>
>[=E2=80=A6]
>
>> we need a kernel option for various open source operating systems
>which
>> causes all UDP to be fragmented at 512 octets of payload=2E
>
>If working on a protocol that merely depends on certain middleboxes
>eventually die is "insanity", what do we call it when people work on a
>protocol that depends on UDP fragments working everywhere?

"Untried=2E"
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E


From nobody Sat Sep 23 05:29:25 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2551201F8 for <dnsop@ietfa.amsl.com>; Sat, 23 Sep 2017 05:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level: 
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_RUURL=3, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OX5_hXf4kZGG for <dnsop@ietfa.amsl.com>; Sat, 23 Sep 2017 05:29:22 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3486133352 for <dnsop@ietf.org>; Sat, 23 Sep 2017 05:29:21 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id c195so3507270itb.4 for <dnsop@ietf.org>; Sat, 23 Sep 2017 05:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=B26+bl0WV8nSnowgaeL+v7v39SZvOdvwRwgefIm9tYg=; b=mGKRoMY/x7ISEXeJammlLY4GJknydo/8xW/u+V3ffx3kfU4rKkzRrJORNsSss2CssG AOi8W6a7DXLEJWH580Uednnivw1VOw3vfwD7io2fQTRnPHeuE8ttMliL7hd430EW7cLx C8euORHzWM8wFUrYu+WNFl890nl9n30QMtK/VL4v/OsacObDrHjAWyhbtC5puvfufRHj iUbl14gCkPkKQQwn+2MIE5U94c/HmRRoJuJIl5C6JWfoh4WWch9+XEEpFCyVrjmaDcae hJRYHeQ7UI2j6MzPXfFLZg4OvI0GIO6SuSdu8OoybxTWus19z+eTTDL9nZ7yPTrE/tsz 64YQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=B26+bl0WV8nSnowgaeL+v7v39SZvOdvwRwgefIm9tYg=; b=pJTiE4+k9pTJS1rWkAU3QvZtmL0L+BJCN9jL8Zzb3DG3yMWFpDQc8R1tdKS2JT0nr7 oPgtmTW9J6UTmMHmqXKid1bdZN4yyL3mAKfjbo8do56PqtwbuuiU+rz4bU4JVPnIPtdZ w6SZh2Ohu4YEFoBChUewGRVXH20MuZsauDXIDvV8QwtZsHZnGdIkV9IOc1hBxbNtF1/T GUrX95O660GfjEkzhAIELVp+Ls0EHlGzUrTX4VEq2pID9cXvcLB7rXhX3b+QxyHNZnBF FaXh96Nse/dpgIoiMiwvofLSOQZ1CxhY+NhKLAO4wMQ0+GFyikzfbxlPpQm0slJVW64p 56Dg==
X-Gm-Message-State: AHPjjUhqiSbiw+7ECSdV8rFJShpjuUfcEhHkjQFHn/K+qujPGOvvW/PD eRs4RuDmGmWgP2hwsCN5brTmpzUlzAgg/iBQ2no=
X-Google-Smtp-Source: AOwi7QB9tvUotttKmQXyS0DQAdi2uXDJrVIvnZ9hT955gSusjNaU5G4JfwhAT8X+Y94r4g3UqVp4NtUz/tuQ7IdNhRw=
X-Received: by 10.36.182.5 with SMTP id g5mr9829246itf.35.1506169761121; Sat, 23 Sep 2017 05:29:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.22.2 with HTTP; Sat, 23 Sep 2017 05:29:20 -0700 (PDT)
In-Reply-To: <59c3307b.1549ca0a.d58f9.40c8SMTPIN_ADDED_BROKEN@mx.google.com>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <59c3307b.1549ca0a.d58f9.40c8SMTPIN_ADDED_BROKEN@mx.google.com>
From: william manning <chinese.apricot@gmail.com>
Date: Sat, 23 Sep 2017 05:29:20 -0700
Message-ID: <CACfw2hiJ3QVHeQtbBWahZX=DiFwBHPgfXeFJE49vOWyXKDdeVA@mail.gmail.com>
To: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
Cc: Davey Song <songlinjian@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="089e08201c54954bd20559da79d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dleD4ucew9ZwzWFS_IqEs---MS4>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiAgRndkOiBJLUQgQWN0aW9uOiBkcmFmdC1z?= =?utf-8?q?ong-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Sep 2017 12:29:24 -0000

--089e08201c54954bd20559da79d7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

there is some evidence to suggest that two factors will drive increasingly
large responses.  first is signing with multiple algorithms and second is
increases in key sizes.  in a worst case model, we have to shift to
the McEliece
cryptosystem, post quantum crypto. for a standard selection of parameters,
the public key is 512 kilobits long.  for quantum computing, key sizes must
be increased by a factor of four due to improvements in information set
decoding.  Attacking and defending the *McEliece cryptosystem*
<https://www.google.com/url?url=3Dhttp://scholar.google.com/scholar_url%3Fu=
rl%3Dftp://nozdr.ru/biblio/kolxo3/Cs/CsLn/Post-Quantum%252520Cryptography,%=
2525202%252520conf.,%252520PQCrypto%2525202008(LNCS5299,%252520Springer,%25=
25202008)(ISBN%2525209783540884026)(239s).pdf%2523page%253D40%26hl%3Den%26s=
a%3DX%26scisig%3DAAGBfm0XEERxI9tL9IfgPGaNOklLIG0r1Q%26nossl%3D1%26oi%3Dscho=
larr&rct=3Dj&q=3D&esrc=3Ds&sa=3DX&ved=3D0ahUKEwiD6ue0pbvWAhVY-GMKHeFKBUIQgA=
MIJygAMAA&usg=3DAFQjCNHV1StJs0Pom6FVNA77UEgVzinRbw>
 - =E2=80=8EBernstein   ....   so, yes, bigger responses should be planned =
for.
Anyone for DNS over BitTorrent?  :)

/Wm

On Wed, Sep 20, 2017 at 8:22 PM, Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) <l=
jsong@biigroup.cn> wrote:

> Thank you.
>
>
>
> The large DNS response in IPv6 is a real problem. ATR is one option to ad=
opted in authoritative  server alone. If someone or party have more influen=
ce on both resolver and authoritative side (cloud and app provider who can =
choose their own DNS resolution path),  Mukund=E2=80=99s proposal to fragme=
nt the DNS message is a good solution.   https://tools.ietf.org/html/draft-=
muks-dns-message-fragments-00
>
>
>
> So I do recommend ATR and DNS message fragments should be both considered
>  in a tool box for large DNS response issues.
>
>
>
> Davey
>
>
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* DNSOP [mailto:dnsop-bounces@ietf.org] *=E4=
=BB=A3=E8=A1=A8 *william manning
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B49=E6=9C=8821=E6=97=
=A5 1:30
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* Davey Song
> *=E6=8A=84=E9=80=81:* dnsop
> *=E4=B8=BB=E9=A2=98:* Re: [DNSOP] Fwd: I-D Action: draft-song-atr-large-r=
esp-00.txt
>
>
>
> i think this is a worthy document for consideration.
>
>
>
> /Wm
>
>
>
> On Sun, Sep 10, 2017 at 9:29 PM, Davey Song <songlinjian@gmail.com> wrote=
:
>
> Hi folks,
>
>
>
> I just submit a draft dealing with issue of large DNS response especially
> in IPv6. Commnets are welcome.
>
>
>
> If chairs think it is in the scope of dnsop wg and encourage us to discus=
s
> it in this mailing list, I can submit it as a draft listed in dnsop wg.
>
>
>
> Davey
>
>
>
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: 11 September 2017 at 10:13
> Subject: I-D Action: draft-song-atr-large-resp-00.txt
> To: i-d-announce@ietf.org
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : ATR: Additional Truncated Response for Large DN=
S
> Response
>         Author          : Linjian Song
>         Filename        : draft-song-atr-large-resp-00.txt
>         Pages           : 8
>         Date            : 2017-09-10
>
> Abstract:
>    As the increasing use of DNSSEC and IPv6, there are more public
>    evidence and concerns on IPv6 fragmentation issues due to larger DNS
>    payloads over IPv6.  This memo introduces an simple improvement on
>    authoritative server by replying additional truncated response just
>    after the normal large response.
>
>    REMOVE BEFORE PUBLICATION: The source of the document with test
>    script is currently placed at GitHub [ATR-Github].  Comments and pull
>    request are welcome.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-song-atr-large-resp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-song-atr-large-resp-00
> https://datatracker.ietf.org/doc/html/draft-song-atr-large-resp-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>
>

--089e08201c54954bd20559da79d7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">there is some evidence to suggest that two factors will dr=
ive increasingly large responses. =C2=A0first is signing with multiple algo=
rithms and second is increases in key sizes. =C2=A0in a worst case model, w=
e have to shift to=C2=A0<span style=3D"font-family:sans-serif;font-size:15.=
75px">the=C2=A0</span><span style=3D"font-family:sans-serif;font-size:15.75=
px">McEliece cryptosystem, post quantum crypto. f</span><span style=3D"font=
-family:sans-serif;font-size:15.75px">or a standard selection of parameters=
, the public key is 512 kilobits long. =C2=A0</span><span style=3D"font-fam=
ily:sans-serif;font-size:15.75px">for quantum computing, key sizes must be =
increased by a factor of four due to improvements in information set decodi=
ng. =C2=A0</span><a href=3D"https://www.google.com/url?url=3Dhttp://scholar=
.google.com/scholar_url%3Furl%3Dftp://nozdr.ru/biblio/kolxo3/Cs/CsLn/Post-Q=
uantum%252520Cryptography,%2525202%252520conf.,%252520PQCrypto%2525202008(L=
NCS5299,%252520Springer,%2525202008)(ISBN%2525209783540884026)(239s).pdf%25=
23page%253D40%26hl%3Den%26sa%3DX%26scisig%3DAAGBfm0XEERxI9tL9IfgPGaNOklLIG0=
r1Q%26nossl%3D1%26oi%3Dscholarr&amp;rct=3Dj&amp;q=3D&amp;esrc=3Ds&amp;sa=3D=
X&amp;ved=3D0ahUKEwiD6ue0pbvWAhVY-GMKHeFKBUIQgAMIJygAMAA&amp;usg=3DAFQjCNHV=
1StJs0Pom6FVNA77UEgVzinRbw" style=3D"color:rgb(102,0,153)">Attacking and de=
fending the=C2=A0<b>McEliece cryptosystem</b></a><span class=3D"gmail-f" st=
yle=3D"color:rgb(128,128,128)">=C2=A0-=C2=A0<cite style=3D"color:rgb(0,102,=
33);font-style:normal">=E2=80=8EBernstein =C2=A0 .... =C2=A0 so, yes, bigge=
r responses should be planned for.=C2=A0 Anyone for DNS over BitTorrent? =
=C2=A0:)</cite></span><div><span class=3D"gmail-f" style=3D"color:rgb(128,1=
28,128)"><cite style=3D"color:rgb(0,102,33);font-style:normal"><br></cite><=
/span></div><div><span class=3D"gmail-f" style=3D"color:rgb(128,128,128)"><=
cite style=3D"color:rgb(0,102,33);font-style:normal">/Wm</cite></span></div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Se=
p 20, 2017 at 8:22 PM, Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) <span dir=3D=
"ltr">&lt;<a href=3D"mailto:ljsong@biigroup.cn" target=3D"_blank">ljsong@bi=
igroup.cn</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lan=
g=3D"ZH-CN" link=3D"blue" vlink=3D"purple"><div class=3D"m_8558659785659908=
473WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-=
size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
f497d">Thank you. <u></u><u></u></span></p><p class=3D"MsoNormal"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><pre><span =
lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1f497d">The large DNS response in IPv6 is a rea=
l problem. ATR is one option to adopted in authoritative =C2=A0server alone=
. If someone or party have more influence on both resolver and authoritativ=
e side (cloud and app provider who can choose their own DNS resolution path=
), =C2=A0Mukund=E2=80=99s proposal to fragment the DNS message is a good so=
lution.=C2=A0=C2=A0 <a href=3D"https://tools.ietf.org/html/draft-muks-dns-m=
essage-fragments-00" target=3D"_blank">https://tools.ietf.org/html/<wbr>dra=
ft-muks-dns-message-<wbr>fragments-00</a> </span><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;color:black"><u></u><u></u></span></pre><p class=3D"Ms=
oNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></sp=
an></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5p=
t;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">So =
I do recommend ATR and DNS message fragments should be both considered =C2=
=A0in a tool box for large DNS response issues. <u></u><u></u></span></p><p=
 class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"f=
ont-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;colo=
r:#1f497d">Davey =C2=A0<u></u><u></u></span></p><p class=3D"MsoNormal"><a n=
ame=3D"m_8558659785659908473__MailEndCompose"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d"><u></u>=C2=A0<u></u></span></a></p><div style=3D"border:none;b=
order-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style=3D"b=
order:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p cla=
ss=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=B6=E4=
=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> DNSOP [mailto:<a href=3D"mailto:dnsop-bounces@ietf.org"=
 target=3D"_blank">dnsop-bounces@ietf.org</a><wbr>] </span><b><span style=
=3D"font-size:10.0pt">=E4=BB=A3=E8=A1=A8 </span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt">william manning<br></span><b><span style=3D"font-s=
ize:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4<span lang=3D"EN-US">:</spa=
n></span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt"> 2017</span><s=
pan style=3D"font-size:10.0pt">=E5=B9=B4<span lang=3D"EN-US">9</span>=E6=9C=
=88<span lang=3D"EN-US">21</span>=E6=97=A5<span lang=3D"EN-US"> 1:30<br></s=
pan><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span la=
ng=3D"EN-US"> Davey Song<br></span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US=
">:</span></b><span lang=3D"EN-US"> dnsop<br></span><b>=E4=B8=BB=E9=A2=98<s=
pan lang=3D"EN-US">:</span></b><span lang=3D"EN-US"> Re: [DNSOP] Fwd: I-D A=
ction: draft-song-atr-large-resp-00.<wbr>txt<u></u><u></u></span></span></p=
></div></div><div><div class=3D"h5"><p class=3D"MsoNormal"><span lang=3D"EN=
-US"><u></u>=C2=A0<u></u></span></p><div><p class=3D"MsoNormal"><span lang=
=3D"EN-US">i think this is a worthy document for consideration. =C2=A0<u></=
u><u></u></span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u=
>=C2=A0<u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN=
-US">/Wm<u></u><u></u></span></p></div></div><div><p class=3D"MsoNormal"><s=
pan lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p><div><p class=3D"MsoNorma=
l"><span lang=3D"EN-US">On Sun, Sep 10, 2017 at 9:29 PM, Davey Song &lt;<a =
href=3D"mailto:songlinjian@gmail.com" target=3D"_blank">songlinjian@gmail.c=
om</a>&gt; wrote:<u></u><u></u></span></p><div><div><p class=3D"MsoNormal">=
<span lang=3D"EN-US">Hi folks,=C2=A0<u></u><u></u></span></p></div><div><p =
class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></d=
iv><div><p class=3D"MsoNormal"><span lang=3D"EN-US">I just submit a draft d=
ealing with issue of large DNS response especially in IPv6. Commnets are we=
lcome.=C2=A0<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><spa=
n lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p class=3D"MsoN=
ormal"><span lang=3D"EN-US">If chairs think it is in the scope of dnsop wg =
and encourage us to discuss it in this mailing list, I can submit it as a d=
raft listed in dnsop wg.<u></u><u></u></span></p></div><div><p class=3D"Mso=
Normal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p c=
lass=3D"MsoNormal"><span lang=3D"EN-US">Davey<u></u><u></u></span></p></div=
><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0<u></u><u></u=
></span></p></div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0=
<u></u></span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US">--------=
-- Forwarded message ----------<br>From: &lt;<a href=3D"mailto:internet-dra=
fts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;<br>Date: 1=
1 September 2017 at 10:13<br>Subject: I-D Action: draft-song-atr-large-resp=
-00.<wbr>txt<br>To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_bla=
nk">i-d-announce@ietf.org</a><br><br><br><br>A New Internet-Draft is availa=
ble from the on-line Internet-Drafts directories.<br><br><br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: ATR: Addition=
al Truncated Response for Large DNS Response<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Linjian Song<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-song-atr-large-re=
sp-00.<wbr>txt<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0: 8<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 : 2017-09-10<br><br>Abstract:<br>=C2=A0 =C2=A0As t=
he increasing use of DNSSEC and IPv6, there are more public<br>=C2=A0 =C2=
=A0evidence and concerns on IPv6 fragmentation issues due to larger DNS<br>=
=C2=A0 =C2=A0payloads over IPv6.=C2=A0 This memo introduces an simple impro=
vement on<br>=C2=A0 =C2=A0authoritative server by replying additional trunc=
ated response just<br>=C2=A0 =C2=A0after the normal large response.<br><br>=
=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the document with tes=
t<br>=C2=A0 =C2=A0script is currently placed at GitHub [ATR-Github].=C2=A0 =
Comments and pull<br>=C2=A0 =C2=A0request are welcome.<br><br><br>The IETF =
datatracker status page for this draft is:<br><a href=3D"https://datatracke=
r.ietf.org/doc/draft-song-atr-large-resp/" target=3D"_blank">https://datatr=
acker.ietf.org/<wbr>doc/draft-song-atr-large-resp/</a><br><br>There are als=
o htmlized versions available at:<br><a href=3D"https://tools.ietf.org/html=
/draft-song-atr-large-resp-00" target=3D"_blank">https://tools.ietf.org/htm=
l/<wbr>draft-song-atr-large-resp-00</a><br><a href=3D"https://datatracker.i=
etf.org/doc/html/draft-song-atr-large-resp-00" target=3D"_blank">https://da=
tatracker.ietf.org/<wbr>doc/html/draft-song-atr-large-<wbr>resp-00</a><br><=
br><br>Please note that it may take a couple of minutes from the time of su=
bmission<br>until the htmlized version and diff are available at <a href=3D=
"http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br><br>Intern=
et-Drafts are also available by anonymous FTP at:<br><a href=3D"ftp://ftp.i=
etf.org/internet-drafts/" target=3D"_blank">ftp://ftp.ietf.org/internet-<wb=
r>drafts/</a><br><br>______________________________<wbr>_________________<b=
r>I-D-Announce mailing list<br><a href=3D"mailto:I-D-Announce@ietf.org" tar=
get=3D"_blank">I-D-Announce@ietf.org</a><br><a href=3D"https://www.ietf.org=
/mailman/listinfo/i-d-announceInternet-Draft" target=3D"_blank">https://www=
.ietf.org/mailman/<wbr>listinfo/i-d-announce<br>Internet-Draft</a> director=
ies: <a href=3D"http://www.ietf.org/shadow.html" target=3D"_blank">http://w=
ww.ietf.org/shadow.<wbr>html</a><br>or <a href=3D"ftp://ftp.ietf.org/ietf/1=
shadow-sites.txt" target=3D"_blank">ftp://ftp.ietf.org/ietf/<wbr>1shadow-si=
tes.txt</a><u></u><u></u></span></p></div><p class=3D"MsoNormal"><span lang=
=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><p class=3D"MsoNormal" styl=
e=3D"margin-bottom:12.0pt"><span lang=3D"EN-US"><br>_______________________=
_______<wbr>_________________<br>DNSOP mailing list<br><a href=3D"mailto:DN=
SOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br><a href=3D"https://ww=
w.ietf.org/mailman/listinfo/dnsop" target=3D"_blank">https://www.ietf.org/m=
ailman/<wbr>listinfo/dnsop</a><u></u><u></u></span></p></div><p class=3D"Ms=
oNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div></div></=
div></div></div></div></blockquote></div><br></div>

--089e08201c54954bd20559da79d7--


From nobody Sat Sep 23 05:34:58 2017
Return-Path: <chinese.apricot@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE8C13336A for <dnsop@ietfa.amsl.com>; Sat, 23 Sep 2017 05:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HCl1P7s5rrcG for <dnsop@ietfa.amsl.com>; Sat, 23 Sep 2017 05:34:55 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C6EE133352 for <dnsop@ietf.org>; Sat, 23 Sep 2017 05:34:55 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id o200so3365078itg.0 for <dnsop@ietf.org>; Sat, 23 Sep 2017 05:34:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=svBoSKuEM8/LDOtQVttRubuau9/78Yz6wVSmXmLQx6g=; b=vSTCgf8rH2Zd5dpBKEPtsmkK3Nmx4l+YD2N9dUOyXNFbQNkWmUsmEmy04IOQuiVLI1 UwXIlP7KdaDZ7y76mwG850qkP0OyOt6N3B9wmvLsZfqGK8bjtYgO4QD7Z73vGLDx86o+ ZeANLspieETK2MYphZbwlCF7aYmeY5obg1sbpmqtyKNx17fmB+pnMes0K1x7KEeh78kJ mAdsK4mE9MIydVuCnSgTIkuni6SolxwAo8sll/fBpQK4u29+DRuYgN36tZGJss4LyL74 qM7RSlU6XPOzCGB87XJfgV9GvPssJqLM0r00qjYU8zaaB6Ue2xYDWucpKEK0kSEOdKkK rtNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=svBoSKuEM8/LDOtQVttRubuau9/78Yz6wVSmXmLQx6g=; b=psPRKmnSDJ3pE9p5S0YOO+bxCMGSQ2ZqHYlEvLi3MUYRFLceR6zlx1Dbvi9OS72wIO rROLY/BGDUjhGFsAJCJ0J557MENsX2x1jnwtfJPAjw1DzSS9ID6PmugL98OJ4Gj1tAaD uHHTq13mvTD5zeX+sudkXZh6Aufbgs3h3/iCzxbzkkbtOi7gfhPpbJgHyp0rc4vaCt0y R/7asJvR2DVQkbXTSGo9jxXdkfnsLQyJ51mSAOSKnLNBXDGBEcD6Si4jW5LXo17u5OsG iTwAvbsQdE6cxYBx+6/eNNOp+W6lR9MPXFYTZ8/i+6haGi9HV8cyiJY2AT4AovA2qSHq GqRA==
X-Gm-Message-State: AHPjjUgJNHXMCHwibAJbIXHNEEkbZF1TfSp+fSnD0u0deOnkn8BSCxHk FlVKt1p4lEbo2+yAjf7HBn470nTZ8J6coDbY6h0=
X-Google-Smtp-Source: AOwi7QDv8TCnl5dG0Go/Ax/ENaDVYRDnJtO0QFIXgEuGcSV8gPwXa8q21yNzrAacCMWmvdaIjJyA1S6U9GLaDGM8f1Q=
X-Received: by 10.36.31.200 with SMTP id d191mr10930141itd.81.1506170094674; Sat, 23 Sep 2017 05:34:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.22.2 with HTTP; Sat, 23 Sep 2017 05:34:54 -0700 (PDT)
In-Reply-To: <59C47601.5030804@redbarn.org>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org> <048701d332a8$6f944980$4ebcdc80$@cn> <59C47601.5030804@redbarn.org>
From: william manning <chinese.apricot@gmail.com>
Date: Sat, 23 Sep 2017 05:34:54 -0700
Message-ID: <CACfw2hjAEEKw53O8jL_Dj0uuumqQZ1mYpWPii66K-gnkywbsKQ@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>,  dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11446e8676e6070559da8dc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hFeL3rcdjZsQ0RSeI6Zqatrvr1A>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiDnrZTlpI06IEZ3ZDogSS1EIEFjdGlvbjog?= =?utf-8?q?draft-song-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Sep 2017 12:34:58 -0000

--001a11446e8676e6070559da8dc3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You wrote; "we can, if we wish, continue to standardize one protocol, watch
as the world deploys a different one, and still pretent that our effort was
worthwhile. however, this would fit the technical definition of "insanity",
and i urge that we avoid this course of action."

The IETF has been doing this for years, why stop now?   Pragmatically, this
is why Randy Bush refers to the IETF as the IVTF.

On Thu, Sep 21, 2017 at 7:31 PM, Paul Vixie <paul@redbarn.org> wrote:

>
>
> Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) wrote:
>
>> Hi Paul,
>>
>> I know you suggest expose the problem and let the trouble maker
>> feeling the pain themselves. But return to the specific issue, from
>> APNIC's measurement the ASes in the path are dropping the fragments,
>> rather than end ASes. From these ASes' view , it's your pain not
>> theirs.
>>
>
> it's a question of first mover advantage. EDNS will never be fully
> deployed, because of the middleboxes built before 1999 who "know" what a
> UDP/53 datagram has to look like, and which disallow ADCOUNT>0 && QR=3D0.
>
> we can, if we wish, continue to standardize one protocol, watch as the
> world deploys a different one, and still pretent that our effort was
> worthwhile. however, this would fit the technical definition of "insanity=
",
> and i urge that we avoid this course of action.
>
> In another word, we are facing the fragmented and uncooperative
>> Internet. What should we do ? It is very hard to coordinate all parts
>> and networks. DNS is a field with lots of tussle.
>>
>
> we need a kernel option for various open source operating systems which
> causes all UDP to be fragmented at 512 octets of payload. for ipv4, so th=
at
> we can hard-smash every middlebox which still prevents EDNS from being
> deployed, and for ipv6 also, so that we can hard-smash any middle or edge
> network who won't carry ipv6 extension headers.
>
> and we need to turn this on everywhere. root, gtld, cctld, recursives,
> authoriatives, 8.8.8.8, opendns... Everywhere. with a press release to
> pre-announce the flag day.
>
> if we're not going to stand up for the standards we write, then we should
> admit that nothing except tcp/80 will work, and avoid all else.
>
> --
> P Vixie
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--001a11446e8676e6070559da8dc3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You wrote; &quot;<span style=3D"font-size:14.4px">we can, =
if we wish, continue to standardize one protocol, watch as the world deploy=
s a different one, and still pretent that our effort was worthwhile. howeve=
r, this would fit the technical definition of &quot;insanity&quot;, and i u=
rge that we avoid this course of action.&quot;</span><div><span style=3D"fo=
nt-size:14.4px"><br></span></div><div><span style=3D"font-size:14.4px">The =
IETF has been doing this for years, why stop now? =C2=A0 Pragmatically, thi=
s is why Randy Bush refers to the IETF as the IVTF. =C2=A0</span></div></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Sep 21,=
 2017 at 7:31 PM, Paul Vixie <span dir=3D"ltr">&lt;<a href=3D"mailto:paul@r=
edbarn.org" target=3D"_blank">paul@redbarn.org</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
Davey Song(=E5=AE=8B=E6=9E=97=E5=81=A5) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Paul,<br>
<br>
I know you suggest expose the problem and let the trouble maker<br>
feeling the pain themselves. But return to the specific issue, from<br>
APNIC&#39;s measurement the ASes in the path are dropping the fragments,<br=
>
rather than end ASes. From these ASes&#39; view , it&#39;s your pain not<br=
>
theirs.<br>
</blockquote>
<br></span>
it&#39;s a question of first mover advantage. EDNS will never be fully depl=
oyed, because of the middleboxes built before 1999 who &quot;know&quot; wha=
t a UDP/53 datagram has to look like, and which disallow ADCOUNT&gt;0 &amp;=
&amp; QR=3D0.<br>
<br>
we can, if we wish, continue to standardize one protocol, watch as the worl=
d deploys a different one, and still pretent that our effort was worthwhile=
. however, this would fit the technical definition of &quot;insanity&quot;,=
 and i urge that we avoid this course of action.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In another word, we are facing the fragmented and uncooperative<br>
Internet. What should we do ? It is very hard to coordinate all parts<br>
and networks. DNS is a field with lots of tussle.<br>
</blockquote>
<br></span>
we need a kernel option for various open source operating systems which cau=
ses all UDP to be fragmented at 512 octets of payload. for ipv4, so that we=
 can hard-smash every middlebox which still prevents EDNS from being deploy=
ed, and for ipv6 also, so that we can hard-smash any middle or edge network=
 who won&#39;t carry ipv6 extension headers.<br>
<br>
and we need to turn this on everywhere. root, gtld, cctld, recursives, auth=
oriatives, 8.8.8.8, opendns... Everywhere. with a press release to pre-anno=
unce the flag day.<br>
<br>
if we&#39;re not going to stand up for the standards we write, then we shou=
ld admit that nothing except tcp/80 will work, and avoid all else.<span cla=
ss=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
-- <br>
P Vixie</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/dnsop</a><br>
</div></div></blockquote></div><br></div>

--001a11446e8676e6070559da8dc3--


From nobody Mon Sep 25 05:01:59 2017
Return-Path: <fweimer@redhat.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C471342D8 for <dnsop@ietfa.amsl.com>; Mon, 25 Sep 2017 05:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 H6TRTb0nTy_d for <dnsop@ietfa.amsl.com>; Mon, 25 Sep 2017 05:01:56 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D84831321A1 for <dnsop@ietf.org>; Mon, 25 Sep 2017 05:01:56 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2743C3D96F; Mon, 25 Sep 2017 12:01:56 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2743C3D96F
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer@redhat.com
Received: from oldenburg.str.redhat.com (ovpn-116-138.ams2.redhat.com [10.36.116.138]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 64A3570BA0; Mon, 25 Sep 2017 12:01:53 +0000 (UTC)
To: Paul Vixie <paul@redbarn.org>, =?UTF-8?B?RGF2ZXkgU29uZyjlrovmnpflgaUp?= <ljsong@biigroup.cn>
Cc: 'Davey Song' <songlinjian@gmail.com>, 'dnsop' <dnsop@ietf.org>, 'william manning' <chinese.apricot@gmail.com>
References: <150509601027.9852.16967877638602485585@ietfa.amsl.com> <CAAObRXJ6wJGCXkbKVkNmQCJ8NccBT63A8-9-LiRVZCFsDicchw@mail.gmail.com> <CACfw2hhaKTyfJfjQ5-_kfqiHX1oX+9P6mUWD06B87y_2ysdztA@mail.gmail.com> <045b01d33288$d3fadad0$7bf09070$@cn> <59C34510.4080705@redbarn.org>
From: Florian Weimer <fweimer@redhat.com>
Message-ID: <9e84000b-fc4e-b92d-58f2-186a3e0b9e65@redhat.com>
Date: Mon, 25 Sep 2017 14:01:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <59C34510.4080705@redbarn.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Mon, 25 Sep 2017 12:01:56 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yREuPkeO5iiko5tY4yyaXMVMfow>
Subject: Re: [DNSOP]  =?utf-8?b?562U5aSNOiBGd2Q6IEktRCBBY3Rpb246IGRyYWZ0LXNv?= =?utf-8?q?ng-atr-large-resp-00=2Etxt?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 12:01:58 -0000

On 09/21/2017 06:50 AM, Paul Vixie wrote:
> both ideas are wrong. what we have to do is arrange to fragment, using 
> the ipv6 extension header, all ipv6 udp, for a period of not less than 
> five years. noone who blocks ipv6 extension headers should be able to 
> get reliable ipv6 udp services. we have to make this problem felt where 
> it is made. we must NOT work around it to insulate the makers of the 
> problem from the costs of their actions.

I disagree with this approach.  Just avoid fragmentation altogether.  We 
know that it's harmful and can be used to bypass existing DNS hardening 
features.  Within five or ten years, packet rates have increased so much 
that the additional protection afforded by the 32-bit reassembly ID in 
IPv6 isn't sufficient anymore, either.

IP fragmentation is dead.  Use something else.

Thanks,
Florian


From nobody Thu Sep 28 03:28:04 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE8B13466D for <dnsop@ietfa.amsl.com>; Thu, 28 Sep 2017 03:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 Dw-B6lx9qvEn for <dnsop@ietfa.amsl.com>; Thu, 28 Sep 2017 03:28:01 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79962134668 for <dnsop@ietf.org>; Thu, 28 Sep 2017 03:28:01 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 82504B1; Thu, 28 Sep 2017 12:27:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1506594479; bh=psPKq2xovfaCjGiJvUHCAP5T+XifhdIY+/Z98yxpm+U=; h=Date:From:To:Subject:From; b=tM9qHZjk4aJ43SL6d7Uj4woRRmXMC61EqHtSfkeaCrGJa2MvzjzskJ44WowvjOi1N 03nsfpZvrkwtZiPHwickv5DcLPOr+v5lmQTwmcyZxqYTmKeCOyZ25WvvKgJ/qX2UUd aBEQZFrN1GBxlAwos9X0r6QK2UR4T0IxS7pd49Wk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6A166AF for <dnsop@ietf.org>; Thu, 28 Sep 2017 12:27:59 +0200 (CEST)
Date: Thu, 28 Sep 2017 12:27:59 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dnsop@ietf.org
Message-ID: <alpine.DEB.2.20.1709281227420.18564@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6O5cC6invwMDcO85yrug3E1kL2U>
Subject: [DNSOP] KSK rollover postponed
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 10:28:03 -0000

https://www.icann.org/news/announcement-2017-09-27-en

Thought this might be relevant to some.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Sep 28 18:11:35 2017
Return-Path: <cheshire@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F15813430B for <dnsop@ietfa.amsl.com>; Thu, 28 Sep 2017 18:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 8UrTXxHWrVV7 for <dnsop@ietfa.amsl.com>; Thu, 28 Sep 2017 18:11:26 -0700 (PDT)
Received: from mail-in22.apple.com (mail-out22.apple.com [17.171.2.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C1A7134499 for <dnsop@ietf.org>; Thu, 28 Sep 2017 18:11:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1506647484; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=yjIB5tTkU6q6d4BZXoBBBKZuRzodDq43ayxnx/Prir8=; b=HmTRRycgCXICElPvJKdrkL2mBgA/qcHntuSUOmVO5vpX+/Sk8MAFfm5MGImXpTev iJZtmdfd/GwzSaXV+YCTtVWd6KMpUUh+KJkKX0z+3nICxbyZGqeJw99/wNM7dU8j td/XM/2jJDaUX5nCs7pG7XVYB1pQshfBrv4QYkEG3CPt8A1H68NvEGTnPRfui8yK plHfPAKCfGkRyKP/XACJrBSfvsc+4bk+jiXxs2LQXbBCFK4jJb9JRn3Hng0X60La MvfMDzsEOHVpLshf1KQikxoYetYItKH/akLgMZm/VqPFw2MCZOw0F3VmjQfKf+5m XC+D4SzBbdnjDRsEEaTJ9A==;
Received: from relay7.apple.com (relay7.apple.com [17.128.113.101]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in22.apple.com (Apple Secure Mail Relay) with SMTP id 2B.F5.14095.CBD9DC95; Thu, 28 Sep 2017 18:11:24 -0700 (PDT)
X-AuditID: 11ab0216-7144d9c00000370f-db-59cd9dbc60b2
Received: from jimbu.apple.com (jimbu.apple.com [17.151.62.37]) by relay7.apple.com (Apple SCV relay) with SMTP id 15.1B.07283.BBD9DC95; Thu, 28 Sep 2017 18:11:23 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Received: from da0602a-dhcp111.apple.com ([17.226.23.111]) by jimbu.apple.com (Oracle Communications Messaging Server 8.0.1.3.20170825 64bit (built Aug 25 2017)) with ESMTPSA id <0OX000NITOMY1250@jimbu.apple.com>;  Thu, 28 Sep 2017 18:11:23 -0700 (PDT)
Sender: cheshire@apple.com
From: Stuart Cheshire <cheshire@apple.com>
Content-transfer-encoding: quoted-printable
Date: Thu, 28 Sep 2017 18:11:21 -0700
Message-id: <23952FC2-2FB5-4FE1-BBDC-F577CCEFB043@apple.com>
To: dnssd@ietf.org, dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDLMWRmVeSWpSXmKPExsUi2FCYqrtn7tlIgxXbLSzuvrnMYvF+6SxG izdrjjA5MHs0XVjG7rFkyU+mAKYoLpuU1JzMstQifbsErowTn/+zFdxmq9i45iNjA+Nt1i5G Tg4JAROJN+8eMnYxcnEICaxlktizbzoTTOLJpilgtpDABkaJWfMFQGxeAUGJH5PvsXQxcnAw C6hLTJmSC9HbyCSx7P86ZpAaYQEpiVcrP4PZbAJaEi8+X2EDsZkFtCWevLsAtphFQFViQ/8h Foh6L4lXk64wQsy3kXh0ogNsrwhQb/ukk1CHykrcmn2JGWSZhMBDVonN/14wT2AUmIXkplkI N81Csm4BI/MqRuHcxMwc3cw8IyO9xIKCnFS95PzcTYyg4FzNJLaD8d5rw0OMAhyMSjy8Bopn I4VYE8uKK3MPMUpzsCiJ897tAAoJpCeWpGanphakFsUXleakFh9iZOLglGpg9OF4uPKyTdbC 62rrHKrZ0qwlr0kpC38qTYnW/6b976Z1SO7iG0brutJdV53MO+EikxQUks4fs+5PoqmRrPaL L9ckl4vdFKxcvdjxvf4OJeE1Trcjgtg59rIH/ig3T+V5+LX54r/4Ww1srGbqSpP2WdicvCnX eXXplVM6S0zPbjV1mX1I9oafEktxRqKhFnNRcSIA8HbqHC8CAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42IRnG6nqrt77tlIg3vzlC3uvrnMYvF+6SxG izdrjjA5MHs0XVjG7rFkyU+mAKYoLpuU1JzMstQifbsErowTn/+zFdxmq9i45iNjA+Nt1i5G Tg4JAROJJ5umMIHYQgIbGCVmzRcAsXkFBCV+TL7H0sXIwcEsoC4xZUpuFyMXUEkjk8Sy/+uY QWqEBaQkXq38DGazCWhJvPh8hQ3EZhbQlnjy7gLYfBYBVYkN/YdYIOq9JF5NusIIMd9G4tGJ DrC9IkC97ZNOQt0jK3Fr9iXmCYy8s5CcMQvhjFlINixgZF7FKFCUmpNYaa6XWFCQk6qXnJ+7 iREUSg2FqTsYG5dbHWIU4GBU4uE1UDwbKcSaWFZcmXuIUYKDWUmE99BkoBBvSmJlVWpRfnxR aU5q8SFGaQ4WJXHe5WuORgoJpCeWpGanphakFsFkmTg4pRoYA6J3M2SdlRK6KDb90ZKJWhmF kce5qpsabGezGK/gWuFdaiLLOEFhqp2M5qdrZXX5WraG/m5vQy0Xidc72Hg8slZ5bzLhxIz5 RxeothUpGdb2bXx0ZW7TZYXUj5qCrSciPhu9ebvTS1G25aPQhtB1693enGzn7P+QavihNbw4 bQLTH4HVrhuVWIozEg21mIuKEwHXaebSIQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RsXa2QhxxUxcIDV-Ty_sMOtu_as>
Subject: [DNSOP] DNSSD (DNS-Based Service Discovery) testing at IETF 100 Hackathon
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 01:11:28 -0000

Ted Lemon and I are planning on doing an interop test of our DNSSD code =
at the IETF 100 Hackathon.

Details can be found here:

=
<https://www.ietf.org/registration/MeetingWiki/wiki/doku.php?id=3D100hacka=
thon>

We are planning to test the following protocols:

DNS Stateful Operations  =
<https://tools.ietf.org/html/draft-ietf-dnsop-session-signal>
DNS Push Notifications   =
<https://tools.ietf.org/html/draft-ietf-dnssd-push>
Service Discovery Proxy  =
<https://tools.ietf.org/html/draft-ietf-dnssd-hybrid>
Service Discovery Relay  =
<https://tools.ietf.org/html/draft-sctl-dnssd-mdns-relay>
Service Discovery Broker =
<https://tools.ietf.org/html/draft-sctl-discovery-broker>

We welcome others to join us at the Hackathon. Please let us know if =
you=E2=80=99d like to come along and join in the testing.

Stuart Cheshire


From nobody Fri Sep 29 11:49:20 2017
Return-Path: <msj@nthpermutation.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C565134239 for <dnsop@ietfa.amsl.com>; Fri, 29 Sep 2017 11:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.com
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 EDepvxAAPoxq for <dnsop@ietfa.amsl.com>; Fri, 29 Sep 2017 11:49:10 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33BE7134237 for <dnsop@ietf.org>; Fri, 29 Sep 2017 11:49:10 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id i50so748943qtf.0 for <dnsop@ietf.org>; Fri, 29 Sep 2017 11:49:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=XXTB+nz4mW+zoMMsFNBkbNeCh1Hcz4ErvZuREyWW1ZA=; b=1vid8+sDOsAl7TMu6jojfn9GW0+a7vkeiYapDMdEYrPORxxQ8uR4qprIdClE7PNmOe D6hfEcX9Zbk5elkmvuIWhHNWATBtM+U9OG54uOnoaDtrC7UAU8/sQnEdjdsupu9Phkag L7eBv8fpvRL4MWC6us49TqBv56rKc+CUTwox4DI8juz/moqTfWsfM/DeMbsrT2Pf4viz CsArAkzWEac6PiRfK8F2b3fQeo7azKHBDyWrxrIyRkxx05Wa/rZ87ZPNAe56c1q4u5IE ssiytT0Ml3eEAYPvia761p8vgpgXfUCJz58bo8YqPMQQf9igG8j8sP0SnVt+5Ak1qKWy SiCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=XXTB+nz4mW+zoMMsFNBkbNeCh1Hcz4ErvZuREyWW1ZA=; b=C1u9sj+2yAO9jIyww21d8TEv3ci/Syr0FAn9EKzXmeG/AwMJ1c+dCAHEuyvjEvTRg1 o8Ru19VLU4um8cokiEvQl+9808HLePbuLfrk5Hsm7nm1q92CvR6uqu5n+sjGd4kpKlzA 8qw/cfkM0XRTi1Pbvt1W4qv1v99ZLt4b3T2RlfluPXTpJUt+rHwWNkT8tfCx/LZwgDqF SH3snuGhFV0yXRFMvvtLp3PQ8jC/88SW9eE7gIr2nAfz4DPc2nQiJKtuMXemdZ+QSLjo b9t0zUm7CJcdNBiOiTD+7nWOcRHLeFzeLJ7q4V5acqDyUhKXrdaaoI1IXdTrPWDh4343 xefA==
X-Gm-Message-State: AMCzsaWft6WqbRqXS8qbVzDFYQUZ1+k94YqpMBHJBXb1HNdrgLJ2oEwk dfMuTdJZaCO4CWQa1P8EsA7RKsTh
X-Google-Smtp-Source: AOwi7QAXI3IeqJeAAhRX1VRDbNriCPDnZ9IVmtMMWvT6ZGAuL+z2yskcKfKMv+7xY5eSdv48OpNRsw==
X-Received: by 10.200.38.170 with SMTP id 39mr7747944qto.114.1506710948400; Fri, 29 Sep 2017 11:49:08 -0700 (PDT)
Received: from [192.168.1.116] (c-69-140-114-191.hsd1.md.comcast.net. [69.140.114.191]) by smtp.gmail.com with ESMTPSA id x17sm3153375qta.17.2017.09.29.11.49.07 for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Sep 2017 11:49:07 -0700 (PDT)
To: dnsop@ietf.org
References: <yblmv5ya5yc.fsf@wu.hardakers.net>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <840723c3-899a-f57b-caa1-48f14b3686e8@nthpermutation.com>
Date: Fri, 29 Sep 2017 14:49:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <yblmv5ya5yc.fsf@wu.hardakers.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iA6ixxHtun78kPNuIyyrWPHQByw>
Subject: Re: [DNSOP] Responding to MSJ review of the previous rfc5011-security-considerations
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 18:49:13 -0000

Comments on -05 and your changes in line.

On 9/13/2017 1:01 PM, Wes Hardaker wrote:
> Mike, after your lengthy last review I went through and carefully made
> sure each of your comments were considered.  Most resulted in changes, a
> few seemed to be just comments and there was nothing to do, and two we
> didn't think were correct.  Below is the summary of the changes in the
> most recent version based on your review from July.
>
> Wes Hardaker
>
>
> Table of Contents
> _________________
>
> 1 Notes / Edits from Mike StJohn on <2017-07-06 Thu>
> .. 1.1 ACCEPTED Use "exclusively" rather than "only" where you can - "only" has
> .. 1.2 ACCEPTED In the introduction  - "validators can update" vs "validators can
> .. 1.3 ACCEPTED In the introduction - same issue with "only recently"
> .. 1.4 ACCEPTED In the introduction - "ceasing publication of a revoked key" vs
> .. 1.5 FIXED Section 1.1 - What is the definition of "rolled"?   Your use of it
> .. 1.6 FIXED Section 2 "which apply to" vs "as required from".
> .. 1.7 FIXED Section 2 "Note that it does not..." - which "it" are you talking about?
> .. 1.8 ACCEPTED Section 2 "using only recently" - same issue as above.
> .. 1.9 ACCEPTED Section 2. New para at "Failure of a DNSKEY..."
> .. 1.10 ACCEPTED Section 2. "... leaving that key in their trust anchor storage
> .. 1.11 ACCEPTED Section 3: Attacker.  "An entity intent..." vs "An attacker
> .. 1.12 FIXED Section 4.1:  This doesn't actually describe what's in 5011 -
> .. 1.13 ACCEPTED Section 4.1, bullet 3:  Same problem with "only".  Instead "Begin
> .. 1.14 REJECTED Section 4.2 last para:  This is only an attack if the private key
> .. 1.15 REJECTED Section 6 - general comment.   You're doing interval calculations
> .. 1.16 FIXED Section 5.1.1 - You're missing a *very* important point here -
> .. 1.17 NOTHINGTODO Section 5.1.1 doesn't actually apply if you use the 5011 rollover
> .. 1.18 FIXED Section 5.1.1, T+35:  "since the hold down time of 30 days + 1/2
> .. 1.19 NOTHINGTODO Section 6 - the formulas are wrong.  I also  don't understand
> .. 1.20 NOTHINGTODO The final formula should be:
> .. 1.21 NOTHINGTODO In any event, the point needs to be made that this attack
> .. 1.22 FIXED The value in 6 regardless of what it is is the wrong value for
<<< skipped lots of stuff that's OK >>>
>
>
> 1.12 FIXED Section 4.1:  This doesn't actually describe what's in 5011 -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    specifically bullet 3 was modified to clarify your concerns, but isn't
>    what was in 5011.  You need to have both here.
>
>    + Result: Intro paragraph added to note we're paraphrasing 5011 at a
>      very high level only.

Nope - not fixed.  You have "This document discusses the following
scenario, which is one of many possible combinations of operations
defined in Section 6 of RFC5011:" followed by "3. Begin to exclusively 
use recently published DNSKEYs to sign the
appropriate resource records."

5011 does not define this as a possible operation.

Instead: "This document discusses the following scenario which is a 
combination of the operations of sections 6.1 and 6.2 but ignores the 
guidance of the first paragraph of section 6 which recommends at least 
two keys per trust point at all times."


>
>
>
>
>
> 1.14 REJECTED Section 4.2 last para:  This is only an attack if the private key
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    is compromised.  In which case, with only a steady state of a single
>    key, you've got lots of other problems.  Basically, in your one in one
>    out with a steady state of one model, once the current private key is
>    compromised you have no ability to fix the problem.  But getting the
>    numbers for figuring out when this change becomes "sticky" correct is
>    useful.
>
>    + Result: I disagree.  The attack is not just about reusing the stale
>      key beyond it's life time.  The attack in this document describes
>      the ability to affect the state of the validator so that it's state
>      doesn't match the desired state of the Trust Anchor Publisher.
>      You're right, that having that state be out of sync isn't useful to
>      an attacker until they can break the key for the trust anchor.  But
>      an attacker performing this "old state" attack means they have years
>      and years to potentially break the key and introduce fake data into
>      the dns zone years potentially years the future.  But in the end,
>      this *is* an attack against the state of the validator, just not of
>      the severity you allude to above.
Strawman alert.

Um... OK.  If you get to this point then you've (the attacker has) got 
to a) identify those resolvers which have the old key, and b) BREAK THE 
KEY and c) figure out how a 40 year old computer is still working and d) 
was NEVER touched by an administrator in all that time.... given that it 
took you 40 years and $100s of Millions of dollars to break the key.

*sheesh*

>
>
> 1.15 REJECTED Section 6 - general comment.   You're doing interval calculations
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    and you want to do date/time wall clock calculations instead.  While
>    the 5011 values are based on intervals from the RRs get to the
>    validator, the publisher has to be looking at absolute times first
>    (e.g. signature inception and expiration, original TTL) and then
>    deltas from those. [Note, this is NOT a new comment - I've made it
>    previously and strongly]
>
>    + Result: You've failed to convince me the text needs to change.
>      Please propose exact wording (or at least an example) that you feel
>      better serves the purpose.  The wall clock and the interval are
>      mutatable between each other.  We are calculating the interval to
>      wait beyond the publication point (waitTime) which is the same as
>      wallclock_now + waitTime.

Here's the deal.  ICANN today signs a whole group of root DNSKEY RRSets 
once every 3 or 6 months (I forget what the interval is for when they 
meet).  I'm not aware of any real security placed on that data once 
signed, but I would venture to guess its not great since its just signed 
data.

What I would do is look at when the current root KSK rollover process 
began and see what the actual expiration dates are for the old signed 
RRSets and then compare it to your calculations.  I know my "Look at the 
last expiration date of any signed RRSet with the old key in it" gives 
me a good fixed point in time to work from.  I know that your "look at 
the signature interval" doesn't without a lot of additional knowledge.

E.g. given the above is your statement in 1.2 unconditionally true? 
Under which circumstances would it not be true?  Could your document be 
interpreted in a way to make 1.2 not true?


>
>    + That being said, I changed the intro text a bit to be a bit more
>      clear about the fact it starts from the publication time.
>
>      + Based on the conversation in Prague, I'll leave it as is but try
>        to clarify a bit about the issue.
>
>
> 1.16 FIXED Section 5.1.1 - You're missing a *very* important point here -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    that DNSKEY RRSets may be signed ahead of their use.  You need to
>    assume that once signed, they are available to be published - even by
>    an attacker.  So wherever you have "signature lifetime" you want
>    something like "latest signature expiration of any DNSKEY RRSet not
>    containing the new key" or at least you want to calculate the
>    date/time value based on that.
>
>    + Result: There are two issues here:
>      1. When we discuss the exact requirements for publication, we should
>         be very very clear about the timing requirements.  I agree.
>      2. We're trying to pass on the concept of the attack in this
>         section, not necessarily a description that exactly covers all
>         possibilities.  So, though I'm all for making it as accurate as
>         we can, I don't think we should make the example text so
>         confusing to cover all the corner cases that no one can follow
>         it.
>      3. It doesn't benefit an attacker to publish the signatures ahead of
>         time. So you're right that anyone can publish new signatures, it
>         really doesn't affect the timing required by the publisher to
>         wait, which is the point of this draft.

The attacker doesn't publish the signatures - the publisher has 
signatures it won't be using....    the publisher signs stuff way in 
advance of publication because getting people together and getting the 
HSM unlocked to sign things is a big huge expensive production. If the 
publisher doesn't think to modify its signing schedule in advance of a 
5011 action, then your interval calculations are less then useless.

>      4. The important take away I take from your text is that any delay
>         between signing and publication will affect the length of time to
>         wait, and I'm sure this is what you mean by needing to calculate
>         via wall-clock (since everything should be based on
>         sigexpiration).
>
>    XXX: With this goal in mind, I've cleaned up the text a bit to make it
>    a bit more clear.
>
>
> 1.17 NOTHINGTODO Section 5.1.1 doesn't actually apply if you use the 5011 rollover
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    approach (section 6.3).  E.g. K_old (and any RRSets it signed) will be
>    revoked the first time K_new is seen and K_standby is the signing key.
>    At this point this reduces to a normal denial of service attack (where
>    you prevent new data from being retrieved by the resolver).  You'd
>    need a different section to do that analysis. [And thinking about it,
>    why is there any practical difference between this attack and a normal
>    denial of service attack in the first place?]
>
>    + Result: As we've both agreed in the past, the attack described in
>      our 5.1.1 section only applies when you sign exclusively with a key
>      that is too new.  So, yes when you are using K_standby, the attack
>      in question doesn't work.  We're only describing the case where
>      there either isn't a K_standby, or when K_standby is also newer than
>      our 'waitTime' time.
>
>    + And, yes by preventing a new key from being accepted as a trust
>      anchor, this is a denial of service attack.  Though one with
>      potentially serious ramifications since it may require manual
>      intervention on all the devices affected by it (unlikely a
>      network-based DDoS attack, it doesn't stop when the attacker stops
>      sending packets; this is long lived until the configuration is
>      manually fixed).

Section 5.1.1 does not apply to preventing a resolver from seeing a 
revocation.  The calculations are different.   You could add a new 
section describing the revocation attack, but I think all you need to do 
is note that at the beginning of 5.1.1 and point to section 6.2 as the 
mitigation math.

>
>
> 1.18 FIXED Section 5.1.1, T+35:  "since the hold down time of 30 days + 1/2
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    the signature validity... " - Two items: Wordsmithing: The hold down
>    time is just the 30 days, not the plus 1/2...  which I *think* given
>    the reference to 2.3 is actually the queryInterval. clarify please.
>    And queryInterval is not actually 1/2 the signature validity - its the
>    MIN (15 days, 10 days (sig life)/2 and 1 day(orig ttl)/2) or 1/2 a
>    day.
>
>    + Result: you're misreading the sentence thinking the holddown time
>      includes the math with the + and onward, where the holddown time was
>      only the 30 minutes.  I'll reword and though I was trying to avoid
>      the much more complex math in the example, you're correct that it's
>      1/2 the queryInterval which has more terms to calculate it exactly.
The new language works.

>
>
> 1.19 NOTHINGTODO Section 6 - the formulas are wrong.  I also  don't understand
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    where you got MAX(originalTTL/2,15 days) - there's no support for this
>    in the text.
>
>    You're misreading the commas.  One of the terms in the outer max
>    clause is "MAX(original TTL of K_old DNSKEY RRSet) / 2".  This is
>    slightly different than what is in the "1/2*OrigTTL" clause in 5011
>    itself.  This is because if the publisher changes TTLs over the course
>    of signing, you have to take the maximum value of any of them, not
>    just the most recent.  (though, to be super-accurate you need to do
>    some math which we might want to describe about when a given TTL is
>    published vs when Knew is introduced).
>
>    Anyway, in the end, the formula in ours draft directly derives from
>    what is in yours.  We do take into account the possibility of multiple
>    TTLs for a given signature set, which 5011 doesn't take into account
>    (and to some extent, it's less important, but only further shows how
>    much variance a resolver might have before accepting a new trust
>    anchor).
>
>    A clear piece of advice for an eventual BCP would be to not change
>    TTLs at the same time you start any 5011 publication or revocation
>    process.

Note that in 6.1 you have 5 terms, but in the fully expanded equation in 
6.1.6 you have 4.  You're missing the safetyMargin which you didn't 
actually define completely in section 6.1.5.
>
>
> 1.20 NOTHINGTODO The final formula should be:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    EarliestDateWhereAttackFails::= latest SignatureExpiration of any
>    DNSKEY RRSet not containing the new key
>
>    [ ... alternate math analysis deleted for brevity ... ]
>
>    + Result: there are multiple ways to list out the math / timing behind
>      this.  You do spell out an alternate way to lay out the math; I
>      believe your purpose was not to offer a replacement but to ensure we
>      agree upon the timing.  I do see that you're using wall-clock type
>      math, which certainly works and should be equivalent to your example
>      start tiem of 5/1/2017 00:00UTC + our waitTime.
>
>    + I do see your point that anyone could publish the data once signed,
>      not just the

Then please write this document to assume people are stupid in how they 
do things (e.g. signing a lot of data that then doesn't get used...)
>
>
> 1.21 NOTHINGTODO In any event, the point needs to be made that this attack
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>    - while real -
>    is a "retail" attack that would be difficult to prosecute by a single
>    attacker across a broad range of end-entities.  This goes to the
>    general model that no publisher of DNS data knows each and every
>    consumer of that data, nor can wait its publication on every consumer
>    getting published data.  The data protocol for DNS is unidirectional
>    and the update protocol in 5011 was designed with that in mind.
>
>    + Result: We never state in the document that the attack was against
>      every validator out there.  It affects only the validators that
>      received replayed key sets and signatures.  We don't dive into the
>      analysis of how difficult it is to achieve such a replay, either
>      directly or by cache poisoning upstream resolvers, or....  That's
>      outside the scope of the document.  Thus, I don't see any change to
>      the text that is needed as I think the text is pretty clear that a
>      replay attack is already necessary in the attack model.

OK.   Section 5 first para should probably be more clear on this, but I 
can live with it.


From nobody Sat Sep 30 17:05:33 2017
Return-Path: <dmahoney@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172FC134488 for <dnsop@ietfa.amsl.com>; Sat, 30 Sep 2017 17:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level: 
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 uaxa3rGlS9DU for <dnsop@ietfa.amsl.com>; Sat, 30 Sep 2017 17:05:28 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E048134481 for <dnsop@ietf.org>; Sat, 30 Sep 2017 17:05:28 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 9E7413AB33B for <dnsop@ietf.org>; Sun,  1 Oct 2017 00:05:26 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10302) id 8965B216C1E; Sun,  1 Oct 2017 00:05:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by bikeshed.isc.org (Postfix) with ESMTP id 878B6216C1C; Sun,  1 Oct 2017 00:05:26 +0000 (UTC)
Date: Sun, 1 Oct 2017 00:05:26 +0000 (UTC)
From: Dan Mahoney <dmahoney@isc.org>
To: dnsop@ietf.org
Message-ID: <alpine.BSF.2.20.1709302358240.45162@bikeshed.isc.org>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
X-OpenPGP-Key-ID: 0xE919EC51
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8IDveGbm3opgF90GCXfajSdR5pY>
Subject: [DNSOP] ISC DLV Registry now running a signed empty zone
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Oct 2017 00:05:29 -0000

All,

Just to let people know via this list:

As of DNS-OARC 27 (where the change was done live) ISC's DLV Registry has 
now been replaced with a signed empty zone (SOA/NS/A/TXT/DNSKEY/RRSIG), 
which will be auto-re-signed with the same keys for the forseeable future.

The IP address for the old DLV web-ui now redirects to ISC's main page, 
but if anyone needs a copy of the last-known zone contents for historical 
purposes, please reach out.

Thanks to the community for your support.

-Dan Mahoney
ISC Operations Group

(also sending to NANOG, et al, apologies for duplicates).

