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

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=20
       SYNTAX       Unsigned32 (0|200..500)=20
       UNITS        "Milliseconds"=20
       MAX-ACCESS   read-write=20
       STATUS       current=20
       DESCRIPTION=20
           " This object specifies the duration of the rpASDTS ring

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

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

             Value of 'pktcSigDevCidMode'     Default value

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

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

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

> 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=20

-->

> Changes were affected to:

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


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

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

    pktcSigDevCidAfterRing    =20

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

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


    E.g.

    pktcSigDevCidAfterRing    =20

    <snip>

          The following table defines the default values
          for this MIB Object, depending on the signal type=20
         (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>

=20

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

 - Added the new MIB OBject to the MIB group 'pktcInternationalGroup'
 - Corrected the incorrect reference to 'pktcSigDevCidMode' in=20
   pktcSigDevVmwiDelayAfterLR=20
      - 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'