[v6ops] Re: SIIT-DC node requirements (single-stack)
"Soni \"It/Its\" L." <fakedme+ietf@gmail.com> Wed, 04 September 2024 23:28 UTC
Return-Path: <fakedme+ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B99A5C18DBAB for <v6ops@ietfa.amsl.com>; Wed, 4 Sep 2024 16:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.893
X-Spam-Level:
X-Spam-Status: No, score=0.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, MANY_SUBDOM=2.999, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1COGfKcmp7ku for <v6ops@ietfa.amsl.com>; Wed, 4 Sep 2024 16:28:08 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6BEC180B62 for <v6ops@ietf.org>; Wed, 4 Sep 2024 16:28:08 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-20688fbaeafso2096105ad.0 for <v6ops@ietf.org>; Wed, 04 Sep 2024 16:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725492488; x=1726097288; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=ELoT94UlHMS5pu1YzePvycAUA7l9qWTInYz+ljetXWI=; b=KyRpyVj2pxqY11ca4wY+76PiEuy5rYpMPa2jE2SbPXdKV/l3/SXS7I39kqNmBoQKHS IOPFWqMVprXhNLYDel3inRDaOUmd5eGMshYWaNG1aPc+iE2r4ZssIBCnAc8tD4u6XM21 m0NGpqzwhd0uy80AOAsdfliaDs57wsWdkHBuZXFtRKn9wZJbDwDnuyHtORCawYjlmcMk Um34cyeqQRDUGjN5gOGuwPomkSebCfQ+ZWPLm3UsV6hKvDORkv2gfdkYXgwvBKV9OKo6 5/f68xOciB1YuNJ5RPLq6BQ9KbDCFpIM7eMnmvDPtuE8VbuwfvT76oK3r1YRt3855dYD 1ljw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725492488; x=1726097288; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ELoT94UlHMS5pu1YzePvycAUA7l9qWTInYz+ljetXWI=; b=MXGIg9Asl2RDekYyC1qpYlN5rsWU/hv1lVyDvfq4ZAhkctuXPR8/+sT3MmLoYshMe+ CayCv3WZd6IdJbVYmka9BpKiowzZITOA2uuq7Zio/mwEs69zfWBuHytaqOQer0ZGlTxA M0deFKz3ndAFpi8hNNgkJXongn1z/Em4BQJ7jeE69WLkoCnJXagPNqMKiCMyT89jnrjP 5llRr3aZYVkMmI5Y/bbXd7ToFzBFW3+MUoXbw7lfV2AaFD3abhIUuOgiiaR/ph1d1q5v m/jvtGCEh+b5B7x5L0oJGcFWljEePgjrbuDFwdG8PSAFeQ/9u3XDTcFVQfNoj23wWIaa 3Beg==
X-Gm-Message-State: AOJu0YxntwQPYMQbLcgdgXRbj/4uu9XzgIBz4Xcy1T7q+4RwvtexC6fy ic3rGyNNhnPHi3m/BiWAM/kxP2mfZui60JsJHoQ+YRCPROjdy0JB8N0+dg==
X-Google-Smtp-Source: AGHT+IEPUlGO44zhWfaTQqBcbstQtbHGGodzglUmjwt7dDxcpODcWwFMLK8lNhzJSL7QOiu548wg5A==
X-Received: by 2002:a17:903:984:b0:203:a0f0:3481 with SMTP id d9443c01a7336-2058417b336mr122284755ad.5.1725492487930; Wed, 04 Sep 2024 16:28:07 -0700 (PDT)
Received: from ?IPV6:2804:431:cfcc:1dc7::536f:6e69? ([2804:431:cfcc:1dc7::536f:6e69]) by smtp.googlemail.com with ESMTPSA id d9443c01a7336-206aea68998sm18288445ad.263.2024.09.04.16.28.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Sep 2024 16:28:07 -0700 (PDT)
Sender: "Soni L." <fakedme@gmail.com>
Message-ID: <865e0078-c09f-4844-a413-54a769e748fd@gmail.com>
Date: Wed, 04 Sep 2024 20:28:00 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Mark Andrews <marka@isc.org>
References: <9aeb66f5-60c7-498e-8def-0a652bd34baa@gmail.com> <38717B23-5D8F-44D1-87C2-F08D2B8FC8FF@isc.org>
Content-Language: en-US
From: "Soni \"It/Its\" L." <fakedme+ietf@gmail.com>
In-Reply-To: <38717B23-5D8F-44D1-87C2-F08D2B8FC8FF@isc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: M3T3XLIW3YJQEGLJD746CTP3HES4EQHS
X-Message-ID-Hash: M3T3XLIW3YJQEGLJD746CTP3HES4EQHS
X-MailFrom: fakedme+ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: SIIT-DC node requirements (single-stack)
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/WjzbfAFrXrrMKVcctg_Oaq9lN7I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>
The IANA stuff is a good point. However, the main advantages of SIIT-DC are to do with routing and packet processing. DNS is an application-level concept, and rDNS/getnameinfo (usually) isn't even part of the kernel, so this probably should be addressed at an application (read: libc) level. (And we are still completely against DNS64, even for reverse records. We'll make an exception for ipv4only.arpa tho, as it was designed and specified as a DNS-based discovery protocol instead of a hack to make IPv4-only domains resolve on an IPv6-only network.) On 2024-09-04 19:35, Mark Andrews wrote: > Well in BIND you would configure this by setting the dns64 clients to > the ’none;’ acl. > > dns64 64:ff9b::/96 { clients { none; }; }; > > alternatively just configure the reverse zone using the reverse database > implementation directly. > > zone “0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.B.9.F.F.4.6.0.0.IP6.ARPA” { > type primary; database “_dns64 dns64 . .”; > }; > > That said IANA should have been directed to create an insecure delegation > for 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.B.9.F.F.4.6.0.0.IP6.ARPA so that it > CAN ACTUALLY BE USED by DNSSEC validating clients. Alternatively IANA > should have been directed to provide a reverse mapping servers. At the > moment the specification is incomplete. > > % dig 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.B.9.F.F.4.6.0.0.IP6.ARPA ns +dnssec > ;; BADCOOKIE, retrying. > > ; <<>> DiG 9.21.0-dev <<>> 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.B.9.F.F.4.6.0.0.IP6.ARPA ns +dnssec > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18718 > ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags: do; udp: 1232 > ; COOKIE: 868e3d961cd944870100000066d8e0370ef8f51ed8e0b258 (good) > ;; QUESTION SECTION: > ;0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.B.9.F.F.4.6.0.0.IP6.ARPA. IN NS > > ;; AUTHORITY SECTION: > ip6.arpa. 752 IN SOA b.ip6-servers.arpa. nstld.iana.org. 2022093211 1800 900 604800 3600 > ip6.arpa. 752 IN RRSIG SOA 8 2 3600 20240925172238 20240904203346 16801 ip6.arpa. d+mwFkGSUCBSWTIhwXbhOHDP0ipcsMDSY3siOF4YoxH6FCVoVJjb968I Wr9c079tOcTYt/bsiG50jg74LsRvxAMSUyFc4wUcF2HELoZmnxHqRN0a ow/yd7g3FWg9i1277zTbdAAWRmXzpol6u2jVbc09hwd3ybc4Tzrm+qzM VzU= > ip6.arpa. 752 IN NSEC 2.0.1.0.0.2.ip6.arpa. NS SOA RRSIG NSEC DNSKEY > ip6.arpa. 752 IN RRSIG NSEC 8 2 3600 20240912101727 20240822081034 16801 ip6.arpa. A9LGpqSVszkgkxNtvq4CAGl4frQsql8WEtM075ON3VBplxlzcafH8mqX PBYVgefSgDF/0RzPS+q6yvDjFg+jrBUpNL983xOqa1YyPeWtAXhHoecZ 5fqN1wHD2f8wAbIfchq5SkBAy/oVG2V171RdlSLCyaUHaVEGONH7WdR5 mIc= > > ;; Query time: 1 msec > ;; SERVER: ::1#53(::1) (UDP) > ;; WHEN: Thu Sep 05 08:33:27 AEST 2024 > ;; MSG SIZE rcvd: 564 > > % > > Mark > > > On 5 Sep 2024, at 05:55, Soni It/Its L. <fakedme+ietf@gmail.com> wrote: > > > > Hello! > > > > Sooo we've noticed using DNS64 with SIIT-DC is optional (thankfully), however... it raises a really big issue with certain applications. We noticed this while setting up IRC: traditionally, IRC daemons will look up the reverse DNS (hostname) of the connecting client, and that doesn't really work in SIIT-DC deployments... (We mean yeah the hostname is generally unimportant for IRC network operation, so it isn't a huge loss, but it's still rather unfortunate.) > > > > We'd like to suggest recommending the use of PREF64 even for a single-stack server, so that getnameinfo can return the appropriate name by querying for the IPv4 reverse DNS - *without* using DNS64, and independently of a SIIT-DC ER. > > > > Thoughts? > > > > (This is also relevant for our "IPv6-only OS" project. That project is still ongoing, tho it increasingly looks like "CLAT-in-libc" is not really viable (mostly due to signals and socket address type-confusion issues). Anyway.) > > > > -- > > plural system (tend to say 'we'), it/she/they, it instead of you > > > > _______________________________________________ > > v6ops mailing list -- v6ops@ietf.org > > To unsubscribe send an email to v6ops-leave@ietf.org > -- plural system (tend to say 'we'), it/she/they, it instead of you
- [v6ops] SIIT-DC node requirements (single-stack) Soni "It/Its" L.
- [v6ops] Re: SIIT-DC node requirements (single-sta… Mark Andrews
- [v6ops] Re: SIIT-DC node requirements (single-sta… Soni "It/Its" L.