[ipcdn] Changes to draft-ietf-ipcdn-pktc-signaling-11

["Sumanth Channabasappa" <[e-mail]>]

Folks,

Find enclosed the changes incorporated into
"draft-ietf-ipcdn-pktc-signaling"
(http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.
txt).

regards
Sumanth


Change #1/3: New MIB Object
-----------

> Rationale:

Excerpts from the email sent by Phillip Freyman to the IPCDN reflector
(dated 3/29)

<!-- Addition of a new MIB Object
pktcSigDevrpAsDtsDuration - this international object sets the duration
of the ring pulse alerting signal prior to CID signaling.  Variations in
national standards cause CID failure if RP-AS is not defined by local
requirements.
-->

<!-- Reason
A situation has been raised in Belgium where the local telephony
requirements exceed the ETSI EN 300 369-1 definition for RP-AS

In the ETSI document RP-AS is defined as 200 ms to 300 ms in duration.

In the Belgium Belgacom document the RP-AS is implied as being 340 ms
and in field experience this as been verified. Some CPE devices do not
respond if the RP-AS is less than 340 ms.

It does not appear that the maximum ETSI value of RP-AS is adequate and
it does not appear that placing CID during the normal ring cadence is
acceptable.

We therefore have two standards which do not overlap and therefore we
must define a new SigMIB object to define the RP-AS duration from the
ETSI 200 ms min to something in excess of the Belgacom nominal value of
340 ms.
-->

> Proposed addition
pktcSigDevrpAsDtsDuration     OBJECT-TYPE 
       SYNTAX       Unsigned32 (0|200..500) 
       UNITS        "Milliseconds" 
       MAX-ACCESS   read-write 
       STATUS       current 
       DESCRIPTION 
           " This object specifies the duration of the rpASDTS ring

             pulse prior to the start of the transmission of the 
             FSK or DTMF containing the Caller ID information. It is  
             only used when 'pktcSigDevCidMode' is set to a value of 
             'rpAsETS'. 

             The following table defines the default values
             for this MIB Object, depending on the signal type 
            (pktcSigDevCidMode) and MUST be followed:

             Value of 'pktcSigDevCidMode'     Default value

             duringringingETS                 0 (not used)
             dtAsETS                          0 (not used)
             rpAsETS                          250 
             lrAsETS                          0 (not used)
             lrETS                            0 (not used)

             An attempt to set this object while the value of 
             pktcSigDevCidMode is not 'rpAsETS' will result in 
             an 'inconsistent value' error." 
       REFERENCE  
           "ETSI-EN-300-659-1 Specification and Belgacom 
            BGC_D_48_9811_30_09_EDOC version 3.3" 
       DEFVAL { 250 } 
       ::= {pktcSigDevConfigObjects 41 } 

          
Change #2/3: Modifications to existing MIB Objects
-----------  

> Rationale:

Comments from Randy Presuhn (3/30, 3/31), Richard Woundy (3/30, 3/31)
and Phillip Freyman (3/31) and offline discussions between authors and
primary contributors

<!-- Discussion summary
Randy requested clarification on the processing of MIB Objects that are
'not used' in certain scenarios. Further clarifications and discussions
revealed that there was a need to clarify 'not used' and its affect on
GET/GETBULK and SET requests. The authors discussed this issue (offline
as well) and decided to clarify this by:
- Defining a 'default value' to indicate 'not used' scenarios
- Mandating an 'inconsistent value' error in case a SET was performed on
a MIB Object that is 'not used' due to certain constraints 

-->

> Changes were affected to:

pktcSigPulseSignalRepeatCount    
pktcSigDevCidAfterRing     
pktcSigDevCidAfterDTAS    
pktcSigDevCidAfterRPAS    
pktcSigDevRingAfterCID    
pktcSigDevCidDTASAfterLR    
pktcSigDevVmwiAfterDTAS    
pktcSigDevVmwiAfterRPAS    
pktcSigDevVmwiDTASAfterLR    
pktcSigDevCidDelayAfterLR  
pktcSigDevVmwiDelayAfterLR    
pktcSigDevrpAsDtsDuration     


Note:
 - A default value of '0' was chosen in all cases (or a range of 0-0 in 
   the first mentioned object)

 - A clarification was provided to indicate when a MIB Object is used
   E.g. 

    pktcSigDevCidAfterRing     

    <snip>
   
       It is only used when pktcSigDevCidMode is set to a value of   
       'duringRingingETS'
    <snip>

  - A normative requirement was added to follow table descriptions for 
    default values. 


    E.g.

    pktcSigDevCidAfterRing     

    <snip>

          The following table defines the default values
          for this MIB Object, depending on the signal type 
         (pktcSigDevCidMode) and MUST be followed:

          Value of 'pktcSigDevCidMode'     Default value

          duringringingETS                 550 ms
          dtAsETS                          0 (not used)
          rpAsETS                          0 (not used)
          lrAsETS                          0 (not used)
          lrETS                            0 (not used)
    <snip>

 

Change #3/3: Editorial and other changes
-----------

 - Added the new MIB OBject to the MIB group 'pktcInternationalGroup'
 - Corrected the incorrect reference to 'pktcSigDevCidMode' in 
   pktcSigDevVmwiDelayAfterLR 
      - correct reference 'pktcSigDevVmwiDelayAfterLR'
 - Updated the draft details (date etc)
 - other minor editorials

Changes as per Rich Woundy's comments (thanks!)
----------------------------------------------
- Updated references for pktcSigDevCidDtmfStartCode,
pktcSigDevCidDtmfEndCode, pktcSigDevVmwiDtmfStartCode, and
pktcSigDevVmwiDtmfEndCode
  from "[ETSI-EN.*]" to "ETSI-EN.* specification"

- Removed 'NOT RECOMMENDED' from list of keywords

- Updated RFC 3291 to RFC 4001 (and removed note regarding "
<draft-ietf-ops-rfc3291bis-01.txt")


Changes not incorporated:
-------------------------
idnits indicates the following 'experimental warnings' that were ignored
(since they are referenced):

  - Unused Reference: 'ETSI-TS-101-909-4' is defined on line 3317, but
not referenced'   [ETSI-TS-101-909-4] ETSI TS 101 909-4:"Access and
Terminals (AT);'

  - Unused Reference: 'ETSI-EN-300-324-1' is defined on line 3336, but
not referenced '[ETSI-EN-300-324-1] ETSI EN 300 324-1 V2.1.1
(2000-04):"V Interfaces'







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