Re: [Dime] End-to-End Identifier Header || RFC 6733

Diaa Saied <> Wed, 12 July 2023 11:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2972FC151B16 for <>; Wed, 12 Jul 2023 04:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.895
X-Spam-Status: No, score=-6.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cxFhBEZDFu1A for <>; Wed, 12 Jul 2023 04:18:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 91357C14F75F for <>; Wed, 12 Jul 2023 04:18:43 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4R1FYS5g3mz6J6t9 for <>; Wed, 12 Jul 2023 19:16:28 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 12 Jul 2023 12:18:37 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 12 Jul 2023 19:18:33 +0800
Received: from ([]) by ([]) with mapi id 15.01.2507.027; Wed, 12 Jul 2023 12:18:31 +0100
From: Diaa Saied <>
To: "" <>, "" <>
CC: "Zhouxiaoyun (Yun)" <>, "Zhangxuefei(Xuefei)" <>
Thread-Topic: [Dime] End-to-End Identifier Header || RFC 6733
Thread-Index: AdmtoogXl4HWproIS96Ay+P9HB66qgA6eKqgACEGFaABaH+XwA==
Date: Wed, 12 Jul 2023 11:18:31 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_006_c53d434f53614a8c94dcdbfcf021e621huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
X-Mailman-Approved-At: Wed, 12 Jul 2023 05:18:17 -0700
Subject: Re: [Dime] End-to-End Identifier Header || RFC 6733
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Jul 2023 11:18:50 -0000

Dear Lionel,

Any update ?

Diaa Said

From: Diaa Saied
Sent: Wednesday, July 5, 2023 10:59 AM
To: '' <>;
Cc: Zhouxiaoyun (Yun) <>; Zhangxuefei(Xuefei) <>
Subject: RE: [Dime] End-to-End Identifier Header || RFC 6733

Hello Lionel,

Thanks a lot for your valuable feedback it's totally clear, the confusion is that below quote is not differentiating between the original request and the retransmitted request as it says "Senders of request message....." and the retransmitted request is considered a 'Sent request' also, so I was thinking if this part need to be edited to be more clear like saying "Originators of request message......" , or stating that "......on each new message"


Diaa Said

From:<> <<>>
Sent: Tuesday, July 4, 2023 6:44 PM
To: Diaa Saied <<>>;<>
Cc: Zhouxiaoyun (Yun) <<>>; Zhangxuefei(Xuefei) <<>>
Subject: RE: [Dime] End-to-End Identifier Header || RFC 6733

Hi Diaa,

The E2E Id is only unique for the sender not for the receiver. It is the reason the tuple [E2E Id | Diameter Id] is used to uniquely identify a message.
"Retransmitted messages" are identical to the messages previously sent. They are messages in the a pending message queue, for which no answer has been received. Therefore they will havethe same E2E Id and the same Origin-Host (Diameter id).

I Hope that this answer to your question.



Orange Restricted
De : DiME <<>> De la part de Diaa Saied
Envoyé : lundi 3 juillet 2023 13:49
À :<>
Cc : Zhouxiaoyun (Yun) <<>>; Zhangxuefei(Xuefei) <<>>
Objet : [Dime] End-to-End Identifier Header || RFC 6733


This is Diaa from Huawei Telecommunications company and I have inquiry about the End-to-End Identifier Header in the diameter message as it's not stated clearly whether the End-to-End Identifier shall be unique on every request including the retransmitted requests or only unique for each new generated request and the retransmitted ones use the same End-to-End identifier, and below I put two snapshots; one from clause#3 (Diameter Header) [left picture] and one from clause#5.5.4 (Failover and Failback Procedures) [right picture] as both mentioned the End-to-End Identifier but in different ways, so please need to know what the standard means exactly in case of retransmission in terms of assigning the End-to-End Identifier

[cid:image002.jpg@01D9B4CB.B93C2E30]              [cid:image005.jpg@01D9B4CB.B93C2E30]

Diaa Said


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.