aboutsummaryrefslogtreecommitdiffstats
path: root/HOWTO/BENCHMARKS.md
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2013-03-15 18:37:56 +0100
committerAnders Svensson <[email protected]>2013-03-18 13:44:03 +0100
commit359bd293d2a3ab65bac48a3fe14fe8b33beffebd (patch)
treebeddfef4dd25c6c7af4ee6d2b167c3c5700603f4 /HOWTO/BENCHMARKS.md
parentda15b3c5fdc9ff96b8d02f4620c879418648d45c (diff)
downloadotp-359bd293d2a3ab65bac48a3fe14fe8b33beffebd.tar.gz
otp-359bd293d2a3ab65bac48a3fe14fe8b33beffebd.tar.bz2
otp-359bd293d2a3ab65bac48a3fe14fe8b33beffebd.zip
Deal with RFC 6733 change to Vendor-Specific-Application-Id
RFC 6733 has changed the arity of Vendor-Id in this Grouped AVP, from 1* in RFC 3588 to 1 in RFC 6773. This impacts the generated dictionary modules: Vendor-Id is expected to be list-valued in the 3588 dictionary, integer-valued in the 6733 dictionary. This, in turn, breaks the independence of capabilities configuration on a service or transport from the dictionary that will be used to encode an outgoing CER or CEA. This commit fixes this by massaging any Vendor-Specific-Application-Id config as appropriate when constructing CER or CEA for a given dictionary.
Diffstat (limited to 'HOWTO/BENCHMARKS.md')
0 files changed, 0 insertions, 0 deletions