[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Megaco] Iq/Ix-controlled IP byte-rate policing (based on H.248.53 tman)



Title: RE: Ix transcoding stage 2 - a new compromise
Hi Thomas,
just read your 091251:
 
http://www.3gpp.org/ftp/tsg%5Fct/WG3%5Finterworking%5Fex%2DCN3/TSGC3_55_Phoenix/Doc/C3-091251.zip
 
Two comments/concerns:
  1. Don't refer ETSI TISPAN TS 102 333!
    because
    - tman v1 was transferred to ITU-T some years ago, H.248.53 is thus the only relevant reference for tman
    - there isn't any IANA registry anymore for the original ETSI package, thus TS 102 333 is really irrelevant in your contribution
  2. Semantic of tman properties
    => cl. 9/H.248.53 is normative, it's not just examples of policer types
    => Iq/Ix got to select a particular policing algorithm (which must be equivalent to cl. 9), or leave it open and then implicitly refer to cl. 9 (i.e., either a Y.1221 or RFC 2216 policer for IP byte-rate policing)
    => I'm concerned that you want introduce a 2nd semantic for tman properties when reading "Interpreting sdr and pdr at the gateway as recommended in Clause 9 of H.248.53 requires ...".
    Again, cl. 9 mandates parameter mappings between H.248 elements and policer types.
    If you are unhappy with the tman semantics, then contribute against H.248.53 itself, but profile-specific package semantics would be the wrong approach in my opinion.
 
Note: reference for tman is H.248.53 (03/09), which supersedes H.248.53 (06/08), - but H.248.53 (03/09) is unfortunately not yet published by ITU-T.
 
Regards,
Albrecht