IETF Logo Mail Archive

[MMUSIC] Question about draft-ietf-rtcweb-mdns-ice-candidates

Roman Shpount <roman@telurix.com> Mon, 14 December 2020 20:06 UTC

Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCC93A1A51 for <mmusic@ietfa.amsl.com>; Mon, 14 Dec 2020 12:06:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-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 nMacOluBiH5K for <mmusic@ietfa.amsl.com>; Mon, 14 Dec 2020 12:06:15 -0800 (PST)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::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 62FB83A1A4F for <mmusic@ietf.org>; Mon, 14 Dec 2020 12:06:15 -0800 (PST)
Received: by mail-oi1-x22f.google.com with SMTP id f132so20568652oib.12 for <mmusic@ietf.org>; Mon, 14 Dec 2020 12:06:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=g0vfhLi5uIOd9YhlOYSMvxBG/WoDJaRiZIGt3xM+WYY=; b=QIC2OtfuHP8WPZT+cRBMOmOsWBb6c+147nGn9H1Y3X7w09Pky13/mKvROMhGzvPlwF QIU7mfq7yDPtauH+fdhPqeQaaGXMHctIdA5IO9x9BxvijGNgk76wwHGizPBYiKRRuNpy d/QezuHoXmgrufYqzGECzepsIMG4pfLXhIivAZtkp54Ax1oAucC348/tGuC6k8o9ozcX GwE1q4RyLk4HNfPjS4fVJ5PxaZv0wT3D6EJKfdehZqDxyeOyzhhNOy7FiZ/PuRCOdgKP TnB5VyT0ZfabnhxcDOM72xAd60aK1bfg24KuMUxs50H0EM13TrJuIl4e8f2PW0A7mg/h sXpQ==
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; bh=g0vfhLi5uIOd9YhlOYSMvxBG/WoDJaRiZIGt3xM+WYY=; b=noLMaZgOgnuVDO1g+f6vyZHmxvk+rqveJNBJvUSIA0jhhjEuoKjhzwxAiPAmVWzq86 NlBpreRLl3dqefAH//GN3tWxIi7IaL3kTgnxLqYOnnHoyybQVRmM1FmJxiuliOBC2OCX 6tB1M8ALDTueTmnP+tAqa9Urr8BRY55i30ibEhgUKkLqTfn2PAwJN4EAzugZ2xHLFwga 0Z5qLonHsk+ff/OazZkMgbKgMg9gpwr0w4101h0WBrlOZWOI7nNjuZXk0i8IYFYACkDp 3SdxtsCIs2GKi8Qr253wQh1pXqPSPF+ponalqfCZ53ZJaYbQCZLxVRxewMdskLi2snQI 3BqQ==
X-Gm-Message-State: AOAM530jLgJ2459gTt5KjwtwVMq1GS/PXAVVNjuztRXk9baP68/oC0jg b2YH/Ck7ONcQkWMiqvPjNGNXZ7cgRqpRHQ==
X-Google-Smtp-Source: ABdhPJx7kZT9fLgD0CCmQAfp2XkLK56jvWRme4ATuR5e3gn8IPasNliHra1bVhqUEtbaihSO3E1OcA==
X-Received: by 2002:aca:5609:: with SMTP id k9mr19881750oib.179.1607976374406; Mon, 14 Dec 2020 12:06:14 -0800 (PST)
Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com. [209.85.167.178]) by smtp.gmail.com with ESMTPSA id g5sm4563840otq.43.2020.12.14.12.06.13 for <mmusic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 14 Dec 2020 12:06:13 -0800 (PST)
Received: by mail-oi1-f178.google.com with SMTP id 9so13446947oiq.3 for <mmusic@ietf.org>; Mon, 14 Dec 2020 12:06:13 -0800 (PST)
X-Received: by 2002:aca:1110:: with SMTP id 16mr18921899oir.12.1607976373357; Mon, 14 Dec 2020 12:06:13 -0800 (PST)
MIME-Version: 1.0
References: <CAOJ7v-1VEsXobYaq0UdOkaGLGbnNH40srDX+tg+OYZivGRVhNw@mail.gmail.com> <c13a7ebd-73d3-4429-3f0c-77071dda62c6@cisco.com> <1509C133-A893-4F44-9859-541B1F31F95B@apple.com> <CA+m752+V5r+-CB=4-ckhTWRUdHy+2Ap1UxRk-2mafDOhFhtGnA@mail.gmail.com> <8f1951af-d0a3-1f05-c3a8-a2a907a8320c@cisco.com> <CAOJ7v-1Aj2jSxPqFzVqvDZz1CP9=KpVGUxpAg16i+63iT5gsNg@mail.gmail.com> <CAOJ7v-3OQDEy_OYnDeU0KWw88m6W0pR_or9CYPiEJuAnEX0W-w@mail.gmail.com> <e14ba43d-ba21-609f-223e-d1f703fb9770@cisco.com> <CA+m752LWz=SkCHGwzBXzMkEyWb3R5A20OVAsjGiGbE8g=6dciA@mail.gmail.com> <7111cec3-35de-7067-6d4f-b62063224d53@cisco.com> <597A03E6-DBD1-4EA1-BFE3-F24FCF028CFC@apple.com> <dde99284-53ba-12fd-af69-62798a811ec3@cisco.com> <CAD5OKxv6f0GeL5xqaVuCtzFLE0Rkzse6LdiSty-4zxYqBm_YFQ@mail.gmail.com> <CAOJ7v-2c7p6+K6aZfyeBNB71X-1aBNFCZtnfb1A-TCtb3ma7-A@mail.gmail.com> <a489fb7e-1d70-e79a-d4a9-683f43b7e691@cisco.com> <CAOJ7v-2tEZkzrdFyQ_64bY+O8XXGkPRUk75Ejnwn36P=KHv+Hw@mail.gmail.com> <4a30a974-fbef-5b79-d91d-43f0ab3abca9@cisco.com> <8C5F94F4-5226-4875-AE25-07D0551566B8@apple.com> <AM0PR07MB386020B236D6C7676DBB150193C70@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAD5OKxuznrD2JtWSo3rKpQFAOhzLpy=HjMvsCs5UVsRi9EDZ4g@mail.gmail.com>
In-Reply-To: <CAD5OKxuznrD2JtWSo3rKpQFAOhzLpy=HjMvsCs5UVsRi9EDZ4g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 14 Dec 2020 15:06:01 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuKx=-grwDkXSFrboXdkbO4KOZBh85aHJaLr+fTyNM48w@mail.gmail.com>
Message-ID: <CAD5OKxuKx=-grwDkXSFrboXdkbO4KOZBh85aHJaLr+fTyNM48w@mail.gmail.com>
To: Youenn Fablet <youenn=40apple.com@dmarc.ietf.org>, Justin Uberti <juberti=40google.com@dmarc.ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008a987305b6722cb8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QOxcOZ6JA4no0t5_SmZ0CgDPtRQ>
Subject: [MMUSIC] Question about draft-ietf-rtcweb-mdns-ice-candidates
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Dec 2020 20:06:17 -0000

I have a general question about MDNS that will affect the
mdns-ice-candidate draft:

Is it possible for an IPv4 MDNS name allocated by one end-point to be
resolved as IPv6 address by another end-point, or visa-versa (IPv6 MDNS
name be resolved as IPv4)?

I specifically would like to know if something like 464XLAT can cause MDNS
resolution results to be converted to a different IP address type.

If this can happen, then the MDNS candidate can generate more than one
local candidate or a candidate of a different address type, affecting
candidate priority. I think the stability of the FQDN candidate resolution,
including the MDNS candidate resolution, can improve if the expected
address type is specified for each candidate as a candidate extension.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email