RE: SigMIB Draft 10
"Woundy, Richard" <[email protected]> Thu, 30 Mar 2006 17:32:22 -0500
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <6EEEACD9D7F52940BEE26F5467C02C73037CF9BC@PACDCEXCMB01.cable.comcast.com> |
This is a multi-part message in MIME format. --===============1287609269== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65449.F54E863C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C65449.F54E863C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks, that makes sense to me. =20 I tend to agree with the direction of Randy Presuhn's comments (copied below). =20 >What is meant by "not used" in the proposed DESCRIPTION clause? Specifically, what happens when processing a get(next/bulk) request and pktcSigDevCidMode is not rpAsETS? =20 Maybe what is implied is "The value of this object is ignored unless pktcSigDevCidMode is rpAsETS."? I agree that the wording could be clearer. =20 >Also, what is the motivation for requiring inconsistent value errors for all set requests when pktcSigDevCidMode is not rpAsETS? If the value is ignored under those circumstances, it would seem simpler to accept it as long as it is within the SYNTAX range. =20 I tend to agree. If the value of the object is ignored when "pktcSigDevCidMode is not rpAsETS", then it should be safe to set the value of the object. Then this object value could be pre-populated (e.g. in a config file), and pktcSigDevCidMode could be set to rpAsETS (e.g. SNMP Set) independently. Although I think this makes sense in theory, I don't know of a particular use case in practice. =20 Looking at the rest of the -10 draft, there are a *lot* of instances where 'inconsistent value errors' are returned, just like this proposal: =20 pktcSigDevCidAfterRing: "An attempt to set this object while the value of pktcSigDevCidMode is not duringringingETS will result in an 'inconsistent value' error." =20 pktcSigDevCidAfterDTAS: "An attempt to set this object while the value of pktcSigDevCidMode is not dtAsETS or lrAsETS will result in an 'inconsistent value' error." =20 pktcSigDevCidAfterRPAS: "An attempt to set this object while the value of pktcSigDevCidMode is not rpAsETS will result in an 'inconsistent value' error." =20 And so forth. Does someone remember why this is specified in this manner? =20 -- Rich -----Original Message----- From: Freyman Phillip-FPF300 [mailto:[email protected]]=20 Sent: Thursday, March 30, 2006 12:17 PM To: Woundy, Richard; [email protected] Subject: RE: [ipcdn] SigMIB Draft 10 Richard, =20 thanks for the comment =20 Per the current Draft: =20 pktcSigDevCidAfterRPAS - this international object sets the delay=20 between the ring pulse alert signal and the transmission of caller=20 id information.=20 =20 where as =20 pktcSigDevrpAsDtsDuration - this international object sets the duration of =20 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. =20 rpAsDtsDuration is how long the RP-AS is applied =20 CidAfterRPAS is the delay (pause) between the RP-AS and the CID =20 Hopefully this explains the differences? =20 Phil =20 =20 _____ =20 From: Woundy, Richard [mailto:[email protected]]=20 Sent: Thursday, March 30, 2006 11:00 AM To: Freyman Phillip-FPF300; [email protected] Subject: RE: [ipcdn] SigMIB Draft 10 Phillip, =20 Pardon my ignorance with this question. What is the difference between the proposed object below ('pktcSigDevrpAsDtsDuration') and the 'pktcSigDevCidAfterRPAS' in the current -10 draft? =20 I am not so much opposed to this change, I just want to understand the rationale better. =20 And since our WG only has two work items left, I would like to finish this document and get it published. =20 -- Rich -----Original Message----- From: Freyman Phillip-FPF300 [mailto:[email protected]]=20 Sent: Tuesday, March 28, 2006 4:53 PM To: [email protected] Subject: [ipcdn] SigMIB Draft 10 Colleagues, 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. In the following text draft, I have defined a new object (#41) with a range of 200-500 ms. Page 7 Add: pktcSigDevrpAsDtsDuration - this international object sets the duration of =20 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. =20 Page 44 Add: =20 pktcSigDevrpAsDtsDuration OBJECT-TYPE=20 SYNTAX Unsigned32 (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 rpAsETS. The =20 following table defines the default values for this object depending on the signal type:=20 pktcSigDevCidMode Default=20 duringringingETS not used=20 dtAsETS not used=20 rpAsETS 250=20 lrAsETS not used=20 lrETS not used=20 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 Page 60 Add last line pktcInternationalGroup OBJECT-GROUP =20 OBJECTS { =20 pktcNcsEndPntConfigMinHookFlash, =20 pktcNcsEndPntConfigMaxHookFlash, =20 pktcNcsEndPntConfigPulseDialInterdigitTime, =20 pktcNcsEndPntConfigPulseDialMinMakeTime, =20 pktcNcsEndPntConfigPulseDialMaxMakeTime, =20 pktcNcsEndPntConfigPulseDialMinBreakTime, =20 pktcNcsEndPntConfigPulseDialMaxBreakTime,=20 pktcSigDevRingCadence, =20 pktcSigDevCidSigProtocol, =20 pktcSigDevCidDelayAfterLR,=20 pktcSigDevCidDtmfStartCode,=20 pktcSigDevCidDtmfEndCode,=20 pktcSigDevVmwiSigProtocol,=20 pktcSigDevVmwiDelayAfterLR,=20 pktcSigDevVmwiDtmfStartCode,=20 pktcSigDevVmwiDtmfEndCode,=20 pktcSigDevrpAsDtsDuration, I understand it may delay Draft 10 but I think it is necessary. Regards, Phillip Freyman Distinguished Member of the Technical Staff Science Advisory Board Associate Motorola, Inc. Connected Home Solutions IPS IP System Engineering 21440 West Lake Cook Road Deer Park, IL 60010 =20 =20 ------_=_NextPart_001_01C65449.F54E863C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns:o =3D=20 "urn:schemas-microsoft-com:office:office"><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <TITLE>Message</TITLE> <META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD> <BODY> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>Thanks, that makes sense to me.</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>I tend=20 to agree with the direction of Randy Presuhn's comments (copied=20 below).</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT size=3D2><FONT face=3DArial=20 color=3D#0000ff>></FONT><FONT face=3DArial color=3D#0000ff>What is = meant by "not=20 used" in the proposed DESCRIPTION clause? Specifically, what happens = when=20 processing a get(next/bulk) request and pktcSigDevCidMode is not=20 rpAsETS?</FONT></FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006>Maybe what is implied is "The = value of this=20 object is ignored<FONT size=3D2><FONT face=3DArial> unless=20 pktcSigDevCidMode is rpAsETS.</FONT></FONT>"? I agree that the wording = could be=20 clearer.</SPAN></DIV> <DIV><SPAN = class=3D969131922-30032006></SPAN> </DIV></FONT></SPAN><SPAN=20 class=3D969131922-30032006><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D969131922-30032006>></SPAN>Also, what is the motivation for = requiring=20 inconsistent value errors for all set requests when pktcSigDevCidMode is = not=20 rpAsETS? If the value is ignored under those circumstances, it would = seem=20 simpler to accept it as long as it is within the SYNTAX=20 range.</FONT></FONT></FONT></DIV></SPAN> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>I=20 tend to agree. If the value of the object is ignored when=20 "pktcSigDevCidMode is not rpAsETS", then it should be safe to set the = value of=20 the object. Then this object value could be pre-populated (e.g. in a = config=20 file), and pktcSigDevCidMode could be set to rpAsETS (e.g. = SNMP Set)=20 independently. Although I think this makes sense in theory, I don't know = of a=20 particular use case in practice.</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>Looking at the rest of the -10 draft, there are a *lot* of = instances=20 where 'inconsistent value errors' are returned, just like this=20 proposal:</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>pktcSigDevCidAfterRing: "An attempt to set this object while = the value of=20 pktcSigDevCidMode is not duringringingETS will result in an = 'inconsistent value'=20 error."</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>pktcSigDevCidAfterDTAS: "An attempt to set this object while = the value of=20 pktcSigDevCidMode is not dtAsETS or lrAsETS will result in an = 'inconsistent=20 value' error."</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>pktcSigDevCidAfterRPAS: "An attempt to set this object while = the value of=20 pktcSigDevCidMode is not rpAsETS will result in an 'inconsistent value'=20 error."</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>And so=20 forth. Does someone remember why this is specified in this=20 manner?</FONT></SPAN></DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff = size=3D2>--=20 Rich</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT=20 face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> = Freyman=20 Phillip-FPF300 [mailto:[email protected]] <BR><B>Sent:</B> = Thursday,=20 March 30, 2006 12:17 PM<BR><B>To:</B> Woundy, Richard;=20 [email protected]<BR><B>Subject:</B> RE: [ipcdn] SigMIB Draft=20 10<BR><BR></FONT></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Richard,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>thanks for the comment</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Per the current Draft:</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D645000917-30032006><FONT = face=3DArial=20 color=3D#0000ff> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = color=3D#000000><FONT=20 size=3D2><FONT face=3D"Courier New"><SPAN = class=3D645000917-30032006> =20 </SPAN>pktcSigDevCidAfterRPAS - this international object sets the=20 <STRONG><FONT color=3D#008000><FONT color=3D#ff0000>delay</FONT>=20 <o:p></o:p></FONT></STRONG></FONT></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = color=3D#000000><FONT=20 face=3D"Courier New"><FONT size=3D2><SPAN style=3D"mso-spacerun: = yes"> =20 </SPAN>between the ring pulse alert signal and the transmission of = caller=20 <o:p></o:p></FONT></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = color=3D#000000><FONT=20 face=3D"Courier New"><FONT size=3D2><SPAN style=3D"mso-spacerun: = yes"> =20 </SPAN>id information. <o:p></o:p></FONT></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20 style=3D"mso-spacerun: yes"><FONT face=3D"Courier New" color=3D#000000 = size=3D2> = </FONT></SPAN><o:p></o:p></P></FONT></SPAN></DIV> <DIV><SPAN class=3D645000917-30032006></SPAN><FONT face=3DArial = color=3D#0000ff=20 size=3D2>where as</FONT></DIV> <DIV><FONT face=3D"Courier New"><FONT = size=3D2></FONT></FONT> </DIV> <DIV><FONT size=3D+0><FONT size=3D2><SPAN class=3D645000917-30032006> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevrpAsDtsDuration – this international object = sets the <FONT=20 color=3D#ff0000 size=3D3><STRONG>duration</STRONG></FONT> of <SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes"> = </SPAN>the=20 ring pulse alerting signal prior to CID signaling.<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN>Variations in = <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>national standards cause CID failure if RP-AS is not defined by = local=20 <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>requirements.<o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: = yes"> </SPAN><o:p></o:p></FONT></P></SPAN></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006>rpAsDtsDuration is how long the RP-AS is=20 applied</SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006>C<SPAN = class=3D645000917-30032006>idAfterRPAS is=20 the delay (pause) between the RP-AS and the=20 CID</SPAN></SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006><SPAN=20 = class=3D645000917-30032006></SPAN></SPAN></FONT></FONT></FONT> </DIV= > <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006><SPAN class=3D645000917-30032006>Hopefully = this=20 explains the differences?</SPAN></SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006><SPAN=20 = class=3D645000917-30032006></SPAN></SPAN></FONT></FONT></FONT> </DIV= > <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006><SPAN=20 = class=3D645000917-30032006>Phil</SPAN></SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D645000917-30032006></SPAN></FONT></FONT></FONT> </DIV> <DIV><BR></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Woundy, Richard=20 [mailto:[email protected]] <BR><B>Sent:</B> Thursday, = March 30,=20 2006 11:00 AM<BR><B>To:</B> Freyman Phillip-FPF300;=20 [email protected]<BR><B>Subject:</B> RE: [ipcdn] SigMIB Draft=20 10<BR></FONT><BR></DIV> <DIV></DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2>Phillip,</FONT></SPAN></DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2>Pardon my ignorance with this question. What is the = difference between=20 the proposed object below ('pktcSigDevrpAsDtsDuration') and the=20 'pktcSigDevCidAfterRPAS' in the current -10 draft?</FONT></SPAN></DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff size=3D2>I am=20 not so much opposed to this change, I just want to = understand the=20 rationale better.</FONT></SPAN></DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff size=3D2>And=20 since our WG only has two work items left, I would like to finish this = document and get it published.</FONT></SPAN></DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial = color=3D#0000ff size=3D2>--=20 Rich</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT=20 face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> = Freyman=20 Phillip-FPF300 [mailto:[email protected]] <BR><B>Sent:</B> = Tuesday, March 28, 2006 4:53 PM<BR><B>To:</B>=20 [email protected]<BR><B>Subject:</B> [ipcdn] SigMIB Draft=20 10<BR><BR></FONT></DIV> <DIV> <P><FONT face=3DArial><FONT size=3D2><SPAN=20 class=3D298504221-28032006>Colleagues,</SPAN></FONT></FONT></P> <P><FONT face=3DArial><FONT size=3D2><SPAN = class=3D298504221-28032006></SPAN>A=20 situation has been raised in Belgium where the local telephony = requirements=20 exceed the ETSI EN 300 369-1 definition for RP-A<SPAN=20 class=3D298504221-28032006>S</SPAN></FONT></FONT></P> <P><FONT face=3DArial size=3D2>In the ETSI document RP-AS is defined = as 200 ms=20 to 300 ms in duration.</FONT></P> <P><FONT face=3DArial size=3D2>In the Belgium Belgacom document the = RP-AS is=20 implied as being 340 ms and in field experience this as been = verified. Some=20 CPE devices do not respond if the RP-AS is less than 340 = ms.</FONT></P> <P><FONT face=3DArial size=3D2>It does not appear that the maximum = ETSI value of=20 RP-AS is adequate and it does not appear that placing CID during the = normal=20 ring cadence is acceptable.</FONT></P> <P><FONT face=3DArial size=3D2>We therefore have two standards which = do not=20 overlap and therefore we must define a new SigMIB object to define = the RP-AS=20 duration from the ETSI 200 ms min to something in excess of the = Belgacom=20 nominal value of 340 ms.</FONT></P> <P><FONT face=3DArial size=3D2>In the <SPAN=20 class=3D298504221-28032006>following text</SPAN> draft, I have = defined a=20 new object (#41) with a range of 200-500 ms.</FONT></P> <P><SPAN class=3D298504221-28032006><FONT face=3DArial size=3D2>Page = 7=20 Add:</FONT></SPAN></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevrpAsDtsDuration – this international object = sets the=20 duration of <SPAN=20 style=3D"mso-spacerun: = yes"> </SPAN><o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: yes"> = </SPAN>the ring=20 pulse alerting signal prior to CID signaling.<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN>Variations in=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: yes"> = </SPAN>national=20 standards cause CID failure if RP-AS is not defined by local=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>requirements.</FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial></FONT></FONT> </P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D+0><FONT=20 face=3DArial size=3D2><o:p><SPAN class=3D298504221-28032006>Page 44=20 Add:</SPAN></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20 style=3D"mso-spacerun: yes"><FONT face=3DArial=20 size=3D2> </FONT></SPAN><o:p></o:p></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevrpAsDtsDuration<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN>OBJECT-TYPE=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>SYNTAX<SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>Unsigned32 (200..500) <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>UNITS<SPAN=20 style=3D"mso-spacerun: = yes"> =20 </SPAN>"Milliseconds" <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>read-write <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>STATUS<SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>current <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>DESCRIPTION <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> =20 </SPAN>" This object specifies the duration of the rpASDTS ring = pulse=20 prior<o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>to the start of the transmission of the = <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN><o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN><o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>following table defines the default values for this = object<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN><o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>depending on the signal type: <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>pktcSigDevCidMode<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN>Default=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>duringringingETS<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN>not used=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>dtAsETS<SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp; =20 </SPAN>not used <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>rpAsETS<SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp; =20 </SPAN>250 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>lrAsETS<SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp; =20 </SPAN>not used <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>lrETS<SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp; =20 </SPAN>not used <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>An attempt to set this object while the value of=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>pktcSigDevCidMode is not rpAsETS will result in=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> &n= bsp;=20 </SPAN>an 'inconsistent value' error." <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes"> =20 </SPAN><o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> =20 </SPAN>"ETSI-EN-300-659-1 Specification and Belgacom=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: = yes"> =20 </SPAN>BGC_D_48_9811_30_09_EDOC version 3.3" = <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN>DEFVAL=20 { <SPAN class=3D298504221-28032006>2</SPAN>50 }=20 <o:p></o:p></FONT></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT = size=3D2><FONT=20 face=3DArial><SPAN style=3D"mso-spacerun: = yes"> =20 </SPAN><SPAN style=3D"mso-spacerun: yes"> </SPAN>::=3D=20 {pktcSigDevConfigObjects 41 } <o:p></o:p></FONT></FONT></P> <P><SPAN class=3D298504221-28032006><FONT face=3DArial size=3D2>Page = 60 Add last=20 line</FONT></SPAN></P><SPAN class=3D298504221-28032006><FONT = face=3DArial=20 size=3D2> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes"> =20 </SPAN>pktcInternationalGroup<SPAN=20 style=3D"mso-spacerun: yes"> = </SPAN>OBJECT-GROUP<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>OBJECTS {<SPAN style=3D"mso-spacerun: yes"> =20 </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20 style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcNcsEndPntConfigPulseDialMaxBreakTime, = <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: = yes"> =20 </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: = yes"> =20 </SPAN><o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevCidDelayAfterLR, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevCidDtmfStartCode, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevCidDtmfEndCode, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevVmwiSigProtocol, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevVmwiDelayAfterLR, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevVmwiDtmfStartCode, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevVmwiDtmfEndCode, <o:p></o:p></FONT></P> <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20 face=3D"Courier New"><SPAN=20 style=3D"mso-spacerun: yes"> =20 </SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P> <P><FONT face=3DArial size=3D2>I understand it <SPAN=20 class=3D298504221-28032006>may delay </SPAN>Draft 10 but I think it = is=20 necessary.</FONT></P> <P><FONT face=3DArial><FONT size=3D2><SPAN=20 class=3D298504221-28032006>Regards</SPAN>,</FONT></FONT></P></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Phillip = Freyman</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Distinguished Member = of the=20 Technical Staff</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Science Advisory Board = Associate</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Motorola, = Inc.</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Connected Home = Solutions=20 IPS</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>IP System = Engineering</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial><FONT size=3D2>21440 West Lake = Cook=20 Road</FONT></FONT></DIV> <DIV align=3Dleft><FONT face=3DArial><FONT size=3D2>Deer Park, IL=20 60010</FONT></FONT></DIV> <DIV align=3Dleft><FONT face=3DArial></FONT> </DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT = face=3DArial=20 color=3D#0000ff = size=3D2></FONT> </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C65449.F54E863C-- --===============1287609269== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPCDN mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ipcdn --===============1287609269==--