[Dots] TR: [IANA #1181897] expert review for draft-ietf-dots-signal-call-home (service-names-port-numbers)

mohamed.boucadair@orange.com Fri, 13 November 2020 08:05 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2933A0E54 for <dots@ietfa.amsl.com>; Fri, 13 Nov 2020 00:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 YRlyDTQJ2--d for <dots@ietfa.amsl.com>; Fri, 13 Nov 2020 00:05:40 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD1B3A0E29 for <dots@ietf.org>; Fri, 13 Nov 2020 00:05:40 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 4CXWKk10PHz4wxr; Fri, 13 Nov 2020 09:07:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1605254858; bh=Z3I3IPsWJbjb/XhV+U3RFjqb2awIpAE/KgbOZMWV1OM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=X/ZaJHgw/OC7xlLnH7q8AR5AUEuh2+KL3IYV5oWwAM3baqiA+mgXibIUQcSK41Fgs HL2dqXDuoV09Dy1YReYAPHoP0jFbtNOOmA4OQOscl/pO82XXMoiYYX4daQL9Nr+eK/ S5CbKpKql35TLEl/1birNSaGznCVZg7lE2hgAY8shhyM/GNMGjapcPihgTwAzuFSwe V/4CkoulttXGd5rsGfHwDLd4AoQ5DUdlp7MVpyph3HtUaR+pNEoSU1k4vUp+eaaXyi JyUqmNTeoAbdocLFQG+frPEX0kJz/6XtoL2YJjIis57TwKtWBxiNRr8OiQ1x41684/ 9ZOLsaNHpFQRA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 4CXWHQ2T9tzFpWq; Fri, 13 Nov 2020 09:05:38 +0100 (CET)
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>, "Benjamin Kaduk (kaduk@mit.edu)" <kaduk@mit.edu>
Thread-Topic: [IANA #1181897] expert review for draft-ietf-dots-signal-call-home (service-names-port-numbers)
Thread-Index: AQHWuUUnhy7Zd6o6BEqxLESzuXjEqKnFln/g
Date: Fri, 13 Nov 2020 08:05:37 +0000
Message-ID: <26112_1605254738_5FAE3E52_26112_375_1_787AE7BB302AE849A7480A190F8B9330315791E0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <RT-Ticket-1181897@icann.org> <rt-4.4.3-16672-1604531738-1164.1181897-37-0@icann.org> <rt-4.4.3-20454-1605220968-507.1181897-37-0@icann.org>
In-Reply-To: <rt-4.4.3-20454-1605220968-507.1181897-37-0@icann.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/LAWvhY53kRLKv7zR4xe1d2oO38U>
Subject: [Dots] TR: [IANA #1181897] expert review for draft-ietf-dots-signal-call-home (service-names-port-numbers)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2020 08:05:42 -0000

Hi All, 

We received this reply from the port expert.

We do have an appendix that explains why we do need a port number: demux two distinct services (one to handle mitigation and another one to request mitigations). When a DTLS connection is received, the node hosting both the base and call home has no means to determine which role it needs to proceed with. 

I'm not sure how we can follow the suggestion to "use two different messages on the same port" especially that we don't define the transport but rely upon existing ones. 

Unless there are other tweaks not already discarded in the past, I suggest we maintain our request.  

Thoughts? 

Cheers,
Med

-----Message d'origine-----
De : Sabrina Tanamal via RT [mailto:drafts-expert-review@iana.org] 
Envoyé : jeudi 12 novembre 2020 23:43
Cc : kondtir@gmail.com; BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>; supjps-ietf@jpshallow.com; valery@smyslov.net; frank.xialiang@huawei.com; rdd@cert.org; kaduk@mit.edu
Objet : [IANA #1181897] expert review for draft-ietf-dots-signal-call-home (service-names-port-numbers)

Dear Authors, 

We have a response from the IESG-designated port expert: 

I do not see sufficient reason for a second port assignment to be made for this single system. At best, they should just use two different messages on the same port.

This request should not be considered in isolation; it is coupled to https://tools.ietf.org/html/draft-ietf-dots-server-discovery.

One service, one port.

=== 

Best regards,

Sabrina Tanamal
Senior IANA Services Specialist

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.