Subject: RE: [ipcdn] RE:ADre-review:draft-ietf-ipcdn-docs-rfmibv2-13.txtTopic:docsIfCmtsCmStatusEqualizationData& docsIfSigQEqualizationData

From: "Eduardo Cardona" <[email-masked]>
Date: Thu, 20 Oct 2005 15:46:33 -0600

Comments from a vendor

Thanks

Eduardo

-----Original Message-----
From: Brecher, Liran
Sent: Wednesday, October 19, 2005 11:13 AM
To: Eduardo Cardona
Cc: Pollak, Lucy
Subject: RE: [ipcdn] RE: AD
re-review:draft-ietf-ipcdn-docs-rfmibv2-13.txtTopic:
docsIfCmtsCmStatusEqualizationData & docsIfSigQEqualizationData

Eduardo,
I would vote for a-2 are but a-1 is OK as well.
Don't see a reason for a-3.
Thanks,
Liran

a-1) Eduardo (Liran?)
a-2) Liran
a-3)

b-1)
b-2) Margo, Eduardo

Options: 
========

a-1) -- Add Main Tap
DocsEqualizerData ::= TEXTUAL-CONVENTION
          1 byte Main Tap Location
          1 byte Number of forward taps per symbol
          1 byte Number of reverse taps per symbol
          1 byte Number of forward taps
          1 byte Number of reverse taps  

a-2) -- do not consider David Hull's flexibility for Reverse Coefficient
spacing for DS equalizer: use straight DOCSIS 1.1 MAC message format
DocsEqualizerData ::= TEXTUAL-CONVENTION
          1 byte Main Tap Location
          1 byte Number of forward taps per symbol
          1 byte Number of forward taps
          1 byte Number of reverse taps  

a-3) Separate US and DS equalization  "formalize DS equalizer format" 

docsIfCmtsCmStatusEqualizationData OBJECT-TYPE
     SYNTAX      DocsUpstreamEqualizerData

docsIfSigQEqualizationData OBJECT-TYPE
     SYNTAX      DocsDownstreamEqualizerData

alternative b-1) 

docsIfSigQEqualizationData OBJECT-TYPE
        SYNTAX      DocsEqualizerData
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "At the CM, returns the equalization data for the downstream
             channel.
             
             At the CMTS, this object is not applicable and might return

             a zero-length OCTET STRING. Note that previous CMTS 
             implementations may instantiate this object in two ways:
             - An equalization value different of the zero-length
               octet string to indicate an equalization average for
               the upstream channel. Those values have vendor 
               dependent interpretation.
             - Return a zero-length OCTET STRING as described below.
             
             A returned zero-length OCTET STRING indicate the value
             is unknown or if there is no equalization data available
             or defined."
        REFERENCE
            "DOCSIS Radio Frequency Interface Specification,
             Figure 6-23."
        ::= { docsIfSignalQualityEntry 7 }

--Note: same compliance statements as in draft 13

alternative b-2) 

docsIfSigQEqualizationData OBJECT-TYPE
        SYNTAX      DocsEqualizerData
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "At the CM, returns the equalization data for the downstream
             channel.
             
             At the CMTS, this object is not applicable and is not 
             instantiated. Note that previous CMTS implementations 
             may instantiate this object in two ways:
             - An equalization value different of the zero-length
               octet string to indicate an equalization average for
               the upstream channel. Those values have vendor 
               dependent interpretation.
             - Return a zero-length OCTET STRING as described below.
             
             A returned zero-length OCTET STRING indicate the value
             is unknown or if there is no equalization data available
             or defined."
        REFERENCE
            "DOCSIS Radio Frequency Interface Specification,
             Figure 6-23."
        ::= { docsIfSignalQualityEntry 7 }

_______________________________________________
IPCDN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ipcdn