[Dime] End-to-End Identifier Header || RFC 6733
Diaa Saied <diaa.said@huawei.com> Mon, 03 July 2023 11:49 UTC
Return-Path: <diaa.said@huawei.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 364E6C151092 for <dime@ietfa.amsl.com>; Mon, 3 Jul 2023 04:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vd3h2RN7sjd3 for <dime@ietfa.amsl.com>; Mon, 3 Jul 2023 04:49:17 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27BE5C14CEFF for <dime@ietf.org>; Mon, 3 Jul 2023 04:49:15 -0700 (PDT)
Received: from lhrpeml100005.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Qvkdb717lz6D8XQ for <dime@ietf.org>; Mon, 3 Jul 2023 19:45:55 +0800 (CST)
Received: from kwepemi500003.china.huawei.com (7.221.188.51) by lhrpeml100005.china.huawei.com (7.191.160.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Mon, 3 Jul 2023 12:49:10 +0100
Received: from lhrpeml500002.china.huawei.com (7.191.160.78) by kwepemi500003.china.huawei.com (7.221.188.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Mon, 3 Jul 2023 19:49:05 +0800
Received: from lhrpeml500002.china.huawei.com ([7.191.160.78]) by lhrpeml500002.china.huawei.com ([7.191.160.78]) with mapi id 15.01.2507.027; Mon, 3 Jul 2023 12:49:03 +0100
From: Diaa Saied <diaa.said@huawei.com>
To: "dime@ietf.org" <dime@ietf.org>
CC: "Zhouxiaoyun (Yun)" <zhouxiaoyun8@huawei.com>, "Zhangxuefei(Xuefei)" <summer.xuefei@huawei.com>
Thread-Topic: End-to-End Identifier Header || RFC 6733
Thread-Index: AdmtoogXl4HWproIS96Ay+P9HB66qg==
Date: Mon, 03 Jul 2023 11:49:03 +0000
Message-ID: <4202898c20854b8983686d7fb59c8208@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.216.158.252]
Content-Type: multipart/related; boundary="_005_4202898c20854b8983686d7fb59c8208huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/kMZYr__xsOO0EvIxGoVKR53hndI>
X-Mailman-Approved-At: Tue, 04 Jul 2023 08:16:34 -0700
Subject: [Dime] End-to-End Identifier Header || RFC 6733
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.39
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, 03 Jul 2023 11:49:18 -0000
Dears, 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@01D9ADBD.7EE82EB0] [cid:image006.jpg@01D9ADBD.7EE82EB0] BR.. Diaa Said
- [Dime] End-to-End Identifier Header || RFC 6733 Diaa Saied
- Re: [Dime] End-to-End Identifier Header || RFC 67… lionel.morand
- Re: [Dime] End-to-End Identifier Header || RFC 67… Diaa Saied
- Re: [Dime] End-to-End Identifier Header || RFC 67… Diaa Saied