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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 01 February 2019 21:17 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 2D627130ED1 for <mmusic@ietfa.amsl.com>; Fri, 1 Feb 2019 13:17:33 -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=hbaJl/oE; dkim=pass (1024-bit key) header.d=ericsson.com header.b=VfCFbBkx
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 SZSoHEEjoLuk for <mmusic@ietfa.amsl.com>; Fri, 1 Feb 2019 13:17:30 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 563EF1312CA for <mmusic@ietf.org>; Fri, 1 Feb 2019 13:17:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/relaxed; q=dns/txt; i=@ericsson.com; t=1549055847; x=1551647847; 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=J0InleAtJk46yikHo6O6Zf6T8deC0Yjl5TJz5YBZsgQ=; b=hbaJl/oE4Xy+CpLHvseb/9tqUVnQE92sU8dS0z/5EiTWwH0oR7S8x3sN211YjYHV YH+805mcNWfnek53WL3rEeBc+tjxwmuShEOun8lKZXJIx5rDkQkFg96Yr5IwnJVY zidjVIlCFDx6ELO8+6X2IDS9pCtwxo9ubuLNubbg2S8=;
X-AuditID: c1b4fb25-209009e000005ff7-c1-5c54b7678952
Received: from ESESSMB505.ericsson.se (Unknown_Domain [153.88.183.123]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 86.B5.24567.767B45C5; Fri, 1 Feb 2019 22:17:27 +0100 (CET)
Received: from ESESSMR503.ericsson.se (153.88.183.112) by ESESSMB505.ericsson.se (153.88.183.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 22:17:03 +0100
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMR503.ericsson.se (153.88.183.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 1 Feb 2019 22:17:03 +0100
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) 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; Fri, 1 Feb 2019 22:17:02 +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=J0InleAtJk46yikHo6O6Zf6T8deC0Yjl5TJz5YBZsgQ=; b=VfCFbBkxm8ONFovLGvzK7dwoDUzyCehgikf+eFU0zsMdYK46lhm/kXDbLEDx7I4sY5BLXKdgs+OMFrulaMufI85EjxOeBx3WULxjqOx5r4w6tXtBCP800jnRliZNlctVo3+LuGx1iyhWUaOipFTAKxwE83NVju/dXfRd/BkuzR4=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3212.eurprd07.prod.outlook.com (10.170.246.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1580.13; Fri, 1 Feb 2019 21:16:55 +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.013; Fri, 1 Feb 2019 21:16:55 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
CC: Justin Uberti <juberti@google.com>, Simon Perreault <sperreault@jive.com>, "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, "mmusic WG" <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
Thread-Index: AQHUulU2uFx8SsiiZk68wi8iILBKkKXLUQeAgAAF3QCAAAwVgIAACK4AgAADoQCAAAJpqQ==
Date: Fri, 1 Feb 2019 21:16:55 +0000
Message-ID: <HE1PR07MB3161679C1754C88B01279A3493920@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>
In-Reply-To: <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.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: [37.136.56.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB3212; 6:BP2y/87cuLmx+0Hw55gic25xvOFFs561kVwVwa7KBKbEh5P4oEizU3R6Qxqv+xoSz1BW+PkBq+/ogreMW4wBEYb+Bk0fT6tZru9w6gYgw5yQLyy3xy/qu0htruv+vk5qQMKCAgNhffAELrcN3vJoAc7E10eaV9MeKTPnjmPkpRLD8yLjYgDz1+RHATQBsPHrizNLPqWQygqV1k9a9beA5tMKqPoSa9Ktqdff9kUcSDxO7gQGsheoKagIxWmf/erD28FLBFHMDRnHd5B3UbGtBRDKHXOxpFvnRfHKSnP8lknCOeZK/lzG/lKMus7vwoM8XI2wcGc01zIbkPA1h5RGZvpn5q1vLAmbCi8KgWsFO3qAp2W+J2UH9OVfuwshl591p1SMt+pDJ0KwHENs2XAKfk0ykxD9/7bMIX65sOKWQL81Dh03N/G0iS75YZToOR340xUAHGmU/TKA4S9IGOXJbQ==; 5:ef906xqG4BYU1c66olg97fQlSXZvXY169NEV71LuCcFyT7MoYc/pQMMuao4lsDjz9f7jmcPvVpvisF1+uQg58fWs9qGKab1cvGZPqLt/wMr7I/cgXHRrLcGKGNG4NDRL56WI5xmbl5d8UVr06w4Z7XzBhuWOq1kAU1TEY8UaMI5GUU0N0UjwvJN5Rr6X/ANEwF2QB0kjrejSVsbqbyRI/Q==; 7:3wzarknytigYpCLqwtfmvFVJHcJhS/PfdF9r2QDKYdwlKPG+Ep5vtsFnJUDtzP1bNG6T7pxmWq/7jViTj98wJWS9tfksQsMn+q+BuSwy6GDTQtMzBL6tW6b95a+o9lDBKeZql5TH+5qKfRVnX6pYHg==
x-ms-office365-filtering-correlation-id: d08360ff-f4e0-4ff0-1148-08d6888a982c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:HE1PR07MB3212;
x-ms-traffictypediagnostic: HE1PR07MB3212:
x-microsoft-antispam-prvs: <HE1PR07MB32123DC67C42011105E4879493920@HE1PR07MB3212.eurprd07.prod.outlook.com>
x-forefront-prvs: 09352FD734
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(346002)(376002)(136003)(366004)(199004)(189003)(6246003)(8676002)(229853002)(6916009)(256004)(6606003)(8936002)(54906003)(81156014)(6436002)(2906002)(53546011)(316002)(6506007)(14454004)(102836004)(5070765005)(106356001)(66066001)(81166006)(53936002)(68736007)(606006)(14444005)(19627405001)(74316002)(71190400001)(478600001)(71200400001)(86362001)(76176011)(105586002)(6116002)(3846002)(1015004)(7696005)(93886005)(7736002)(99286004)(54896002)(6306002)(9686003)(186003)(26005)(55016002)(486006)(236005)(476003)(97736004)(11346002)(44832011)(446003)(33656002)(4326008)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3212; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: nUZof7AElP1kHWrx8JW/Cc/e4pcQG4fRhVzYcMqFGa7L8JRFyd8G+PPCOI6hEsNmoWVtYVM/xxrvfMwrSZHs9teXMd6xbuJDFN0ASNLpSXY8Q14S8GJU6BvOi2yyI4Smy3sFWIpG46J9VYSQ9DZONlTCNmxlP2AAHKhzBJ4gCvcTkSKBfiTzLQACVUr3mpAOLhjwRKf+tZzo1qreeNxwvK/eu2GcVlQb+zp13AZi9up4+gtv/lbVHf0xaaN28AuyMY27sbJU/w6ICd+UWxMulP+p/qc6FADVkxrVMdpM4Qvia4lvimmikhenfzxRaAGYBT8L0palNNTu2pgYZEli/IaBor9CuHbf+jaS6umJIHMdNujoyRWqi2BoG/q91TJsOWYWBeQI9aFharqyDgJRpvxtV8cTDhSOKTdBsr6Uvus=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161679C1754C88B01279A3493920HE1PR07MB3161eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d08360ff-f4e0-4ff0-1148-08d6888a982c
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2019 21:16:55.7581 (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: HE1PR07MB3212
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTURjHObv37l6Xo+t8e3zLGlrgeyZ4P4TYp4YQJGiK+LbypuJ0tunQ onAGSUoozoHKQkWpMI00TYnQmmKWoZmSNUsUV6JpWLSsrGvbjkXffv///znPc57DYQjZBOXL 5BeV8JoipUoulpBNqQMXwnMHktKj2u/6cP1GGWe8uUxyjS+MBNctVNHc3GwytzquixcrDMM2 QtHaW6ro6PghUgim94TC0lB8kkqTHM3hVfk6XhMZly3Jmx+rQcUmXdl14VIFas+pRi4MsDHQ N7FNVCMJI2NHEWxZKkVY2BD0zNxC/4TpzpfdpF0Etv4rlEOQbB0Bwy2NFE7qRbC28FyMxZL9 TOeavQHDiFkOaoRQx0QPNhh+bxmcrQj2PgLrlGOiC+POquDnh2YCFxVCT+2rXT4FI9O3xQ4m 2SDQm7coB0vZdLBZqkg8bI6G7qEx2hG4sInQ/7bR2RSxXrD1rMvJBOsNFmuLCO/NQsfDKQKz J6wuCxSuV8Jw5+Kuvx+eLFgR5gB42VLjfA1gK2lom6/YDU7AozkDhYM3CITaDQoHIbC2uENj LoCuzR4Ssz8Mfn9H4wP1Yli+XCWuQ+HN/90Qsxo2bF/pZueqbvC0yUpiPwJeGxvEmEPhRttH AnM4NApm8n+/FdGdyFPLa08X5kYfieA1+We0WnVRRBFf0ovsX+xx33bwIJpZP2ZGLIPkrlJ9 Z1K6jFLqtOWFZgQMIfeQWvrtljRHWX6e16izNKUqXmtGfgwp95b+krmly9hcZQlfwPPFvOZv KmJcfCtQ2IPFyaxM03GP5KFA14srosjswJRvCZOzXhlnr7lmRna5raS656znHlBXJ+yLWvoc 364/lJY2uiZZyO7jZqQGhTVlSD0aMa736hLo1cqST+5CnSlmbyBd1XYudI9tc9tgu3dVVZ9Y 5neQyxsJl0SXhgXs+PhPT8TGlvdkBMV5yUltnvJwCKHRKv8A3gL9QF4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wny3LlbgTpInH6BbIjRxjknBofE>
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: Fri, 01 Feb 2019 21:17:33 -0000

Hi,

> 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.

I suggest MUST be ignored, perhaps with a note saying that a future specification will have to define how to use FQDNs that return multiple results.

> Would this work for everyone?

It would work for me.

Regards,

Christer



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