D.3 MC Service Server and Configuration Management Server behaviour

29.2833GPPDiameter data management applicationsRelease 17TS

When performing next hop Diameter Agent selection for requests that are routed based on realm, the MC Service Server/Configuration Management Server may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [17].

Annex E (informative):
Change history

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

Feb 2016

CT4#72

C4-161515

Creation

0.1.0

Feb 2016

CT4#72

C4-161516

Version after Ct4#72

0.2.0

Mar 2016

CT#71

CP-160120

Presented for information and approval

1.0.0

Mar 2016

CT#71

CP-160162

TS number added and Approved

1.0.1

Mar 2016

CT#71

Version 13.0.0 created after CT plenary

13.0.0

Jun 2016

CT#72

CP-160227

0001

2

Enhancements to MCPTT-2 and CSC-13

13.1.0

Jun 2016

CT#72

CP-160227

0002

2

IANA assigned application Id and command code values

13.1.0

2016-12

CT#74

CP-160664

0006

Correction to change IETF drmp draft version to official RFC 7944

13.2.0

2016-12

CT#74

CP-160681

0005

1

Load Control

14.0.0

2017-03

CT#75

CP-170045

0007

1

Support of MCVideo and MCData Services

14.1.0

2017-03

CT#75

CP-170048

0010

1

Update of reference for the Diameter base protocol

14.1.0

2017-03

CT#75

CP-170048

0011

1

Handling of the Vendor-Specific-Application-Id AVP

14.1.0

2017-06

CT#76

CP-171022

0013

Vendor-Specific-Application-Id

14.2.0

2017-06

CT#76

CP-171018

0015

1

Support for signaling transport level packet marking

14.2.0

2017-09

CT#77

CP-172013

0017

Correction of DRMP Procedures

14.3.0

2018-06

CT#80

Update to Rel-15 version (MCC)

15.0.0

2019-09

CT#85

CP-192094

0019

2

draft-ietf-dime-load published as RFC 8583

15.1.0

2020-07

CT#88e

Update to Rel-16 version (MCC)

16.0.0

2022-04

Update to Rel-17 version (MCC)

17.0.0

2022-12

CT#98e

CP-223075

0025

A

Data Pull improvement

17.1.0