Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 05 February 2019 19:52 UTC

Return-Path: <christer.holmberg@ericsson.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 857CB13121F for <mmusic@ietfa.amsl.com>; Tue, 5 Feb 2019 11:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.852
X-Spam-Level:
X-Spam-Status: No, score=-8.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=ericsson.com header.b=eZKvO9v5; dkim=pass (1024-bit key) header.d=ericsson.com header.b=l7/zh4OK
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 2vCzuhO-hV9x for <mmusic@ietfa.amsl.com>; Tue, 5 Feb 2019 11:52:54 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 778EF13121D for <mmusic@ietf.org>; Tue, 5 Feb 2019 11:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed; q=dns/txt; i=@ericsson.com; t=1549396371; x=1551988371; 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=83GZQUo+GG+MWYiQbd7fU6xg635/scO/IaMIJnlZh80=; b=eZKvO9v5fHlc7Pxqa54BGHh4y8NVRYDZOQJ9TN+5ljQiq6KQBdw149UN6OnUjcuM Hd59Q2fsPmv+7jadLQ4uJ9UcN1Ji9+gQLWfs+z6QQEOxZWVaN3mRUVkSwOKuPkn5 O73bppbyB1keB2AjJrxFjuejLgTpsy6YMpWN/lXQlZA=;
X-AuditID: c1b4fb30-f93ff7000000355c-e3-5c59e993a91f
Received: from ESESBMB502.ericsson.se (Unknown_Domain [153.88.183.115]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 0B.6B.13660.399E95C5; Tue, 5 Feb 2019 20:52:51 +0100 (CET)
Received: from ESESSMB501.ericsson.se (153.88.183.162) by ESESBMB502.ericsson.se (153.88.183.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 5 Feb 2019 20:52:50 +0100
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Tue, 5 Feb 2019 20:52:51 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=83GZQUo+GG+MWYiQbd7fU6xg635/scO/IaMIJnlZh80=; b=l7/zh4OKHlqUMquWoxlcgdM4wSmH5vPnVLoNv+Kj2e4IYBS0dCi+gBlQTpFQ1V/9kXkolmeE3hc1dO8vx+AA3fidpK6iRUMvauP5vodxlhc4As1eTQBV11Ul6t4C24yQHpCXIWrH5xLSYChMDdwApnJmYhqlqMmLaB6Bu0QPhSg=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3098.eurprd07.prod.outlook.com (10.170.244.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1601.14; Tue, 5 Feb 2019 19:52:49 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::ec90:1d14:9549:fdf0%4]) with mapi id 15.20.1601.016; Tue, 5 Feb 2019 19:52:49 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alan Ford <alan.ford@gmail.com>, Roman Shpount <roman@telurix.com>
CC: Simon Perreault <sperreault@jive.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUvWQJ5AXujZ/OCkayq1rv1scozqXRnTFt
Date: Tue, 5 Feb 2019 19:52:48 +0000
Message-ID: <HE1PR07MB3161A360F1C281127CCFDCF5936E0@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com>, <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
In-Reply-To: <24551658-0943-431C-B319-D74B5DC169B9@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [87.93.22.227]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3098; 6:7yH1A2AwzUDzFMxlPqDbixEaPBvS4dbXiwoxb6L4UAJBHAl1o+SaSvhP1fo5EWgFqf7H3Qsb8XfUxp20aAOQ7HvDRm3zyT5lYDDvqTW/2pidXxxUYLdopiizx9sOoHTlu73C/MuqfOmU98i0oxh4IHuroiHkZLkwO74NTsjjW+HHvHQw+0w9vewqKstzBWFYrMRGEMIgpW31/2YM32H7/mA9IjYCrlmupbEetNKZ4bbgdPVR+oesCyL+G+rZTvGLPVQAkZIVD+G9ct5oGaWmgS9FYityKWrMLgVqgBXCu2vBYmUSMtyWTschnTAgZOGH59wmsohIkpucLVMAiCST180IZRFx1x3Pgm+7QWuVUXpNPq7R8JsW3/uslmgTUzLDg8IchONEqh638hHmvnBC+HkW8MhyjoNop1XF2zmNTxRF6Gcjp7BcNxbdJcXAzzVYuyo5J3iA5iIFFam2pswxHQ==; 5:jYSbY3kbci3ap5zF5XKlYTbEVYpTe1r8hNMfI9FYzOsmTFCv1iOp/wi1BPYELSWktWrxKMR1nPFos1D+qaX7GG+3gendjlZ235vG08bnlRCs3hQKBOGmFr37Em3/JiILBPDkswHXnuNufJiAHZiIXIYftBhqyazWOwqJFNwM5VuS70cx0OJlznJvL4sCKYPclB8N4RuKraxazQGtBrWTzQ==; 7:eZ6+eeLOhpb4mqIbEMoOp3LoJY9YVMIiuqqhp7lPyFoMsp70DLtC0220I23nJLT7xtKVpgXdHHJYjI8veLr3GkU8cbztNk0d5PlXFdXUBnK6UZxwQb68BwTNovS8Krt6aN08LyQ+D6X3/7HbQZKlng==
x-ms-office365-filtering-correlation-id: e8e6c23b-7d62-4011-3628-08d68ba381a8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3098;
x-ms-traffictypediagnostic: HE1PR07MB3098:
x-microsoft-antispam-prvs: <HE1PR07MB3098BEF1FE47988B8C937ED4936E0@HE1PR07MB3098.eurprd07.prod.outlook.com>
x-forefront-prvs: 0939529DE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(136003)(366004)(39860400002)(346002)(189003)(199004)(54896002)(6306002)(66066001)(3846002)(9686003)(4326008)(7736002)(14454004)(97736004)(478600001)(6116002)(93886005)(236005)(606006)(19627405001)(966005)(8936002)(6506007)(53546011)(102836004)(71200400001)(71190400001)(81166006)(186003)(26005)(99286004)(7696005)(76176011)(446003)(110136005)(54906003)(11346002)(476003)(105586002)(2906002)(106356001)(1015004)(316002)(55016002)(6436002)(33656002)(81156014)(8676002)(68736007)(6606003)(25786009)(486006)(229853002)(14444005)(53936002)(6246003)(44832011)(74316002)(256004)(5070765005)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3098; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: if4/YqnPkSxO6JnmfTqTu7wIiSUPd/BisBhjPQ4qFLsHT8LipF+5fgSN+0qyqZS9ysumat0dhZJAi92f6EWpqVFYUxKzqHsouQAO6OKGLYJxklM1W5Xz2jN8yPXFRfSYJOdzgFGWHKnuyIGIO+gJlOSXXsGaDbZ9MtuCuOW1ov4l6sLI5EbD4Mynby+VzPz1fDuuy+Wive+0jTEcwrYu4JudEZ4i4uZJK+/ZqSd+YR3ecJGdzQMdVUj8jSdCaihhOulsrlQVFoTvjy4wZJUYmjQmXefkY/A8Kv0kBnY/v2PRWcgh3HD2g0YdQj8KTVdZ4Asv7RGr4Y+c8V2g3c/t4zqYwhJKgKYY0wZKV7bRhCxOnGpbUpdLBC/iKqhxJT5LsriXAi6ND70q9JbaiH6/PGN611UiFZoYggw+xZ8ng44=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161A360F1C281127CCFDCF5936E0HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e8e6c23b-7d62-4011-3628-08d68ba381a8
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2019 19:52:48.9307 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3098
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTURzGO3vf7X23Gh2Xlz9aGkMMpk6TyH3QSAixRChLyBjoytcL6pS9 yzIJLFrJVqapeMlbuTLNC4qikk4dRuqHrBCvdBGnsso+VBaWjJzHwG+///95Hp5zDoelZFah J5um1XM6rSZDLpLQled7+MASe7w6+M9DH1XT62eUqqxxkVZVvCmjVK2OO4xqejLuuDCqr+o9 E2U2rwuiHNVLVNRcafZp+oIkLInLSMvhdEHHEiWptnYTlV14G13tthiYfFStMyIxC/gIFHbc p41IwsrwCILJXpOIDGsI7IaebaVBAK+GChjnQOMiCl6slCBnXoZLNpWlcOJaQDBjKdvMs6wI q8Dk8Hd6XHEklCwXipxM4RRw1C1TTt6HM2BlsI0mnkyo6cpHhEOg7Vu9wMk09oWG1o2trBSr wVhajUiXkYXRKQvl7BLjcDD/iHF6EHaH3+MtAtLlAXO2OgG5JwZz/wRF2A3siw4h8WtgsPnT 9v4gdAwZt/kAvKszbXUBvsnA1MQSQ4QYKF+1MUSYRWCZeykkggJsH0YQ4XSoqm3eDuyH3r5h AQlUi8B07zNNno6DxlYDKkIBVTtOSzgL2isMWyzFLjBWaaPJXgkzZaUiwv7w9NEXinAgVDis 9M59PWKakRvP8RczU0JClJwu7RLPZ2mVWk7fiTZ/1nDX3+BeZF+JsCLMIvkeafJCvFom1OTw uZlWBCwld5UGdG+upEma3GucLitBdzmD463Ii6XlHtINmYtahlM0ei6d47I53X9VwIo985H7 oY95EcrkaPVaXXfigH9I1620rKkAa//uk8Vva/amd5oTUq94N6zHjo+f8CoIHms7lSebFuZm 3/UK/uqj0M+Ieov9EgZWj7cZXH3jQr2bciXu2G/Ucr1/17nHz+fFQd9r51vOzoau/kJnmOjy By1hlQk3fi5KAmqeKMyRsYr4o3KaT9UcVlA6XvMPL+LiP1UDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HSeUqE_vIbXNGbaHvDc_oePcixA>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
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: Tue, 05 Feb 2019 19:52:56 -0000

Hi,



>If that update was to be made, this goes against the text in draft-ietf-rtcweb-mdns-ice-
>candidates-02 which says:
>
>  An ICE agent that supports mDNS candidates MUST support the situation
>   where the hostname resolution results in more than one IP address.
>  In this case, the ICE agent MUST take exactly one of the resolved IP
>  addresses and ignore the others.  The ICE agent SHOULD, if available,
>use the first IPv6 address resolved, otherwise the first IPv4 address.

This is what I have previously commented. The text needs to be modified.

Regards,

Christer



On 1 Feb 2019, at 21:06, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:

In this case section 4.1 of ice-sip-sdp should be updated to allow FQDN in connection-address and, perhaps specify that FWDN which return multiple results should be ignored.

Would this work for everyone?

Regards,
_____________
Roman Shpount


On Fri, Feb 1, 2019 at 4:02 PM Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:
I have no problem with allowing FQDNs - as long as they result in a SINGLE address:port.

If we want to define ICE usage of FDNSs resulting in MULTIPLE addresses:ports, I really think that should be a separate document - it should NOT be added as a last minute thing to draft-ice-sip-sdp.

...and, yes, perhaps such work would also affect 8445.

Regards,

Christer





________________________________
From: rtcweb <rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>> on behalf of Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Sent: Friday, February 1, 2019 10:22 PM
To: Justin Uberti
Cc: Simon Perreault; Dale R. Worley; RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?

On Fri, Feb 1, 2019 at 2:39 PM Justin Uberti <juberti@google.com<mailto:juberti@google.com>> wrote:
This has all been discussed at length in rtcweb and I don't think any significant changes are needed, although I tend to think that we should restore the removed FQDN text from mmusic-ice-sip-sdp, which is the only thing not in alignment at this point in time.

I agree that FQDN should be put back into connection-address definition, but  the portion which talks about handling it is completely broken..

Quoting 5245<https://tools.ietf.org/html/rfc5245#section-15.1>.1>:

   <connection-address>:  is taken from RFC 4566<https://tools.ietf.org/html/rfc4566> [RFC4566<https://tools.ietf.org/html/rfc4566>]6>].  It is the
      IP address of the candidate, allowing for IPv4 addresses, IPv6
      addresses, and fully qualified domain names (FQDNs).  When parsing
      this field, an agent can differentiate an IPv4 address and an IPv6


      address by presence of a colon in its value - the presence of a
      colon indicates IPv6.  An agent MUST ignore candidate lines that
      include candidates with IP address versions that are not supported
      or recognized.  An IP address SHOULD be used, but an FQDN MAY be
      used in place of an IP address.  In that case, when receiving an
      offer or answer containing an FQDN in an a=candidate attribute,
      the FQDN is looked up in the DNS first using an AAAA record
      (assuming the agent supports IPv6), and if no result is found or
      the agent only supports IPv4, using an A.  If the DNS query
      returns more than one IP address, one is chosen, and then used for
      the remainder of ICE processing.



I think it was discussed in quite a detail why using a random DNS resolution result is not going to work here..

The only options we have here are:

a. Fix FQDN connection address handling. Probably the most logical way of dealing with this would be to specify that candidate with FQDN should be converted as a result of DNS resolution into multiple candidates, with each candidate corresponding to A or AAAA record in DNS query result. We will also need to specify how FQDN candidate gets applied to c= line address. Something that says IN IP4 FQDN, if any A records exist for this DNS name and IN IP6 FQDN if only AAAA records exist. Once candidate is nominated, address family in c= line should match address family used for communications. This will definitely require a lot more work and discussion.

b. Specify that FQDN connection addresses should be ignored until their handling is defined in a future specification. This seems easy and only requires a sentence or two to fix.

Regards,
_____________
Roman Shpount
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic