Re: [Dime] Question about the changes from RFC3588

<lionel.morand@orange.com> Mon, 17 July 2017 14:53 UTC

Return-Path: <lionel.morand@orange.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC276131C3C for <dime@ietfa.amsl.com>; Mon, 17 Jul 2017 07:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 hFwwDdsO3jEI for <dime@ietfa.amsl.com>; Mon, 17 Jul 2017 07:53:07 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AD6E131C41 for <dime@ietf.org>; Mon, 17 Jul 2017 07:52:56 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 88FF0C0D18; Mon, 17 Jul 2017 16:52:54 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 549B0120082; Mon, 17 Jul 2017 16:52:54 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0352.000; Mon, 17 Jul 2017 16:52:54 +0200
From: <lionel.morand@orange.com>
To: Misha Zaytsev <misha.zaytsev.rus@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Question about the changes from RFC3588
Thread-Index: AQHS8zPdwgvtijx8lE6LLznwVivKtqJYL4sg
Date: Mon, 17 Jul 2017 14:52:53 +0000
Message-ID: <29366_1500303174_596CCF46_29366_111_1_6B7134B31289DC4FAF731D844122B36E2D1B5ECB@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <CABPQr26882ASYySyJOphQDO_DMWk6=x2uFqNLSX5GApz5V17CQ@mail.gmail.com>
In-Reply-To: <CABPQr26882ASYySyJOphQDO_DMWk6=x2uFqNLSX5GApz5V17CQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E2D1B5ECBOPEXCLILM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/MpLjQEiB6xccvqhDO-eyejWiAsI>
Subject: Re: [Dime] Question about the changes from RFC3588
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 14:53:09 -0000

Hi,

I was not able to point to a specific email exchange or discussion on this topic. But I think the change of order between TCP and SCTP is only due to the context of publication.

At the time of RFC3588, it was assumed that SCTP would be largely deployed and available.
Working on the RFC6733 (RFC3588-bis), if you want to deploy Diameter in a secure way, (TLS/)TCP based implementations were still much more available than (DTLS/)SCTP. So if any recommendation was useful at this time, it was natural to propose to start with TCP first and then SCTP.

Regards,

Lionel

De : DiME [mailto:dime-bounces@ietf.org] De la part de Misha Zaytsev
Envoyé : dimanche 2 juillet 2017 15:05
À : dime@ietf.org
Objet : [Dime] Question about the changes from RFC3588

Hi All,

In RFC3588, ch. 2.1:

When connecting to a peer and either zero or more transports are

specified, SCTP SHOULD be tried first, followed by TCP.
In RFC6733, ch. 2.1:

When connecting to a peer and either zero or more transports are

specified, TLS SHOULD be tried first, followed by DTLS, then by TCP,

and finally by SCTP.
What was the reason behind to change the order between TCP and SCTP?
Could anyone help to sort out this point?

Thanks a lot in advance!

/Misha







_________________________________________________________________________________________________________________________

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.