From ipcdn-bounces@ietf.org Wed Mar 01 10:55:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FETfI-0001hi-6c; Wed, 01 Mar 2006 10:55:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FETfG-0001hb-UC
	for ipcdn@ietf.org; Wed, 01 Mar 2006 10:54:58 -0500
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FETfE-0003V4-Bq
	for ipcdn@ietf.org; Wed, 01 Mar 2006 10:54:58 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k21Fsmca020568; 
	Wed, 1 Mar 2006 09:54:49 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <DVB4Y23T>; Wed, 1 Mar 2006 16:54:47 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15509721AEC@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, ipcdn@ietf.org
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information B
	ase for Data-Over-Cable Service Interface Specification Compliant
	CableMo
	dem s and Cable Modem Termination Systems' to Proposed Standard
Date: Wed, 1 Mar 2006 16:54:45 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ihemail2.lucent.com id
	k21Fsmca020568
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606
Cc: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
	Jean-Francois Mule <jf.mule@cablelabs.com>,
	Brian Hedstrom <B.Hedstrom@cablelabs.com>, rdroms@cisco.com
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

A nit:

The DESCRIPTION clause of the MODULE-IDENTITY states:
           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html."

- I would change "The initial version" to "This version".=20
  Because we really want people to look at this RFC which has this
  version and not the initial version of RFC2669.
- I would remove the last sentence:
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html.
  because this is a standalone MIB module and is not maintained
  by IANA at all. So IANA notices on copyrights do not apply I think.
  I vaguely recall I had mentioned this earlier... but anyway.
  Indeed I did mention it om 25 Nov 2005.

I know I have the above in an RFC-Editor note, but since you post a new
rev anyway, I rather would see you fix it.


Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Monday, February 27, 2006 16:45
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> Jean-Francois
> Mule; Woundy, Richard
> Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information
> Base for Data-Over-Cable Service Interface Specification Compliant
> CableModem s and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> I incorporated the changes mentioned below in a preliminary=20
> draft,=20
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.txt>, with the XML version at=20
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.xml>.
>=20
> Your comments are solicited and encouraged; this is the=20
> version I currently plan to submit on March 3rd if all goes well.
>=20
> I performed all of the same checks (online idnits tool,=20
> xml2rfc validator tool, and smilint) on this draft version,=20
> and got the same results (basically clean) as performed in=20
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html>.
>=20
> As I edited the current draft, I discovered we needed one=20
> more update. We "anticipated" outbound LLC filters in the=20
> DOCSIS QoS MIB draft in section 3.3.4; now that the DOCSIS=20
> QoS MIB is published as RFC 4323, the text needed to be=20
> corrected. In addition, I needed to update the reference to=20
> the permanent RFC number, of course.
>=20
> OLD TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet=20
> just prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but it is=20
> anticipated that
>    the Quality of Service (QoS) additions to the DOCSIS standard
>    [I-D.ietf-ipcdn-qos-mib] may include some outbound LLC filtering
>    requirements.  If so, those filters would be applied as described
>    there.
>=20
> NEW TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet=20
> just prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but section 3 of the
>    DOCSIS Quality of Service (QoS) MIB, [RFC4323], includes=20
> outbound LLC
>    filtering requirements.
>=20
> -- Rich
>=20
> -----Original Message-----
> From: Woundy, Richard=20
> Sent: Monday, February 27, 2006 12:34 AM
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> Jean-Francois Mule; Woundy, Richard
> Subject: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information Base for Data-Over-Cable Service Interface=20
> Specification Compliant CableModem s and Cable Modem=20
> Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> This note summarizes the editor and WG chairs' response to=20
> the IETF Last Call comment received on 12/19/2005 by the IESG=20
> from Brian Hedstrom <b.hedstrom@cablelabs.com> on the ID:=20
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> v2-10.txt.
>=20
> This email response has been previously shared with Brian=20
> Hedstrom and we believe it addresses the comment raised by=20
> him, based on existing product implementation and best common=20
> practices from DOCSIS cable operators.
>=20
> In short, we propose to address Brian's comment by adding=20
> clarification text in the current IPCDN MIB module to indicate:
>=20
> 1) CM implementations must report the *first* Syslog server=20
> from the DHCP log server option value if the DHCP option=20
> received by the CM was multi-valued, and
>=20
> 2) CM implementations must report the *active* time server=20
> from the DHCP time server option value if the DHCP option=20
> received by the CM was multi-valued.
>=20
> Let us know if there are any objections to this response by=20
> Friday March 3rd 5pm Eastern Time (note that the draft=20
> submission cut-off is Monday March 6th 9am ET). If there are=20
> no objections by this time, we will post the revision to the=20
> draft including only these two modifications and minimal=20
> editorial changes e.g. draft version, posting date, revision=20
> date, etc. Then we believe the IETF Last Call process will be=20
> complete, and we will assume the draft can proceed=20
> immediately to IESG evaluation and approval.
>=20
> Rich and Jean-Fran=E7ois Mul=E9
> --- Rich as Editor of the IPCDN ID and both as IPCDN co-chairs
> ---
>=20
> In introduction, the chairs would like to note the following:
>    a) the IPCDN Internet-Draft in question is an update to=20
> RFC 2669 (the original IPCDN Cable Device MIB) published in=20
> August 1999. The multi-valued options in DHCP are specified=20
> in RFC 2132 which was published prior to RFC2669 in March=20
> 1997, so the current MIB module restrictions for a single=20
> time server and single log (Syslog) server have been around=20
> for over six years, without any WG, vendor or cable modem=20
> operator comments raised during the updating of the RFC based=20
> on the inability for the MIB objects to reflect multi-value options;
>    b) existing implementations and current DOCSIS cable modem=20
> compliance indicate that most manufacturers do effectively=20
> treat the log server options as single valued;
>    c) most operators do rely on various, multiple mechanisms=20
> to provide server redundancy for Syslog servers; and
>    d) existing implementations and current DOCSIS (1.1 and=20
> 2.0) cable modem compliance indicate that most manufacturers=20
> do effectively treat the time server options as multi valued=20
> for the purpose of determining a functional time server for a=20
> single boot-time time synchronization event, per DOCSIS RFI=20
> 1.1 section 9.2.7 and DOCSIS RFI 2.0 section 11.2.7.
>=20
> Furthermore, the Syslog server MIB object is read-writeable=20
> meaning that, after the CM completes DHCP, the CM may=20
> download a configuration file from the operator's OSS systems=20
> containing SNMP 'Set' commands for that MIB object. This=20
> provides cable operators additional flexibility and is yet=20
> another indicator that best common practice is to use a=20
> single value to set that option in the CM configuration files.
>=20
> This being said, we thank Brian for his comment and we=20
> believe that the comment should be taken into account to add=20
> clarification text in the 2 relevant MIB objects so that new=20
> implementers faced with the same questions know how to=20
> proceed for DOCSIS 1.x and 2.0. Even though we are not aware=20
> of inconsistent implementations, or the practical needs to=20
> address this concern, this may guarantee "more" consistency=20
> in the future. As for future versions of DOCSIS, operator=20
> guidance should be requested on these topics.
>=20
> --- Brian's comment:
> See full details at:=20
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01837.html
>=20
> In summary, the comment raises a question on the support of=20
> multiple Syslog servers in the CM due to the limitations of=20
> docsDevEvSyslogAddress object when the CM is provided with=20
> multiple server values in DHCP Option 7.
>=20
> As Rich pointed out in:=20
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01838.html
> the latest DOCSIS RFI specification available at:=20
> <http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-05
> 1209.pdf>,
> in annex D.1.1, and RFC 2132, defines 5 DHCP options. Three=20
> of out the five standard DHCP options specified are allowed=20
> to be multi-valued:
> * Option code 3 (Router Option)
> * Option code 4 (Time Server Option) -> docsDevServerTimeAddress
> * Option code 7 (Log Server Option)  -> docsDevEvSyslogAddress
>=20
> Note that the Router Option is not referenced by any MIB=20
> object in this MIB module.
>=20
> Based on the rationale explained above in introduction of=20
> this email, we propose to add the following text to the=20
> following objects in
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
v2-10.txt:

- docsDevServerTimeAddress:
NEW TEXT:
   docsDevServerTimeAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "The Internet address of the RFC 868 Time server
                as provided by DHCP option 4.=20

                Note that if multiple values are provided to the=20
                CM in DHCP option 4, the value of this MIB object
                MUST be the Time server address from which the Time
                of Day reference was acquired based on the DOCSIS=20
                RFI specification. During the period of time where
                the Time of Day have not been acquired, the Time=20
                server address reported by the CM may report the=20
                first address value in the DHCP option value or the
                last server address the CM attempted to get the Time
                of day value.

                Returns the zero length octet string if the time server
                IP address is not provisioned."
           REFERENCE
               "DOCSIS RFI 1.1 Specification, Section 9.2.7. and
                DOCSIS RFI 2.0 Specification, Section 11.2.7."
           ::=3D { docsDevServer 9 }


- docsDevEvSyslogAddress:
NEW TEXT:
   docsDevEvSyslogAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-write
           STATUS      current
           DESCRIPTION
               "The Internet address of the Syslog server as provided by
                DHCP option 7 or set via SNMP management.  If the
                address of the server is set to any of the zero length
                string, the 0.0.0.0 IPv4 address or the 0: IPv6 address,
                Syslog transmission is inhibited. =20

                Note that if multiple values are provided to the CM in
                DHCP option 7, the value of this MIB object MUST be the
                first Syslog server address received.

                By default at agent boot, this object returns the zero
                length string."
           ::=3D { docsDevEvent 10 }

We believe this addresses the comment by indicating how current implement=
ations deal with this situation.
------------------------------------------------------------------

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Wed Mar 01 21:13:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEdJi-0002px-1O; Wed, 01 Mar 2006 21:13:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEdEh-0006rL-Nu
	for ipcdn@ietf.org; Wed, 01 Mar 2006 21:08:11 -0500
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEdBc-0003I4-Nk
	for ipcdn@ietf.org; Wed, 01 Mar 2006 21:05:03 -0500
Received: from ([10.20.9.172])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.17346326;
	Wed, 01 Mar 2006 21:04:31 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 1 Mar 2006 21:04:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information Base
	for Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed Standard
Date: Wed, 1 Mar 2006 21:02:30 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF75A@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [ipcdn] Last Call: 'Cable Device Management Information Base
	for Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed
	Standard
Thread-Index: AcY9SIkvyokh+YLGQZ6gMOgOLnAxMgAU8u7w
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
	<ipcdn@ietf.org>
X-OriginalArrivalTime: 02 Mar 2006 02:04:10.0616 (UTC)
	FILETIME=[989C0780:01C63D9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65215b440f7ab00ca9514de4a7a89926
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>, "Woundy,
	Richard" <Richard_Woundy@cable.comcast.com>,
	Brian Hedstrom <B.Hedstrom@cablelabs.com>, rdroms@cisco.com
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Thanks, Bert. So here is the resulting change in my private copy of the =
draft (to be submitted on Friday).

OLD TEXT

           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html."

NEW TEXT

           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). This version
                of this MIB module was published in RFC XXXX; for full
                legal notices see the RFC itself."

In addition, my copy of the draft needed a similar modification as =
discussed for the DOCSIS RF MIB per =
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01870.html>.

OLD TEXT

2.4.  DOCSIS or Data-Over-Cable Service Interface Specification

   "Data-Over-Cable Service Interface Specification".  A term referring
   to the ITU-T J.112 [ITU-T_J.112] Annex B standard for cable modem
   systems.  [RFI1.0] [RFI1.1] [RFI2.0]

NEW TEXT

2.4.  DOCSIS or Data-Over-Cable Service Interface Specification

   "Data-Over-Cable Service Interface Specification".  A term referring
   to the ITU-T Recommendation J.112 [ITU-T_J.112] Annex B standard for
   cable modem systems.  [RFI1.0] [RFI1.1] [RFI2.0]

-- Rich

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
Sent: Wednesday, March 01, 2006 10:55 AM
To: Woundy, Richard; ipcdn@ietf.org
Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com; Jean-Francois =
Mule
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information =
Base for Data-Over-Cable Service Interface Specification Compliant =
CableModem s and Cable Modem Termination Systems' to Proposed Standard


A nit:

The DESCRIPTION clause of the MODULE-IDENTITY states:
           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html."

- I would change "The initial version" to "This version".=20
  Because we really want people to look at this RFC which has this
  version and not the initial version of RFC2669.
- I would remove the last sentence:
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html.
  because this is a standalone MIB module and is not maintained
  by IANA at all. So IANA notices on copyrights do not apply I think.
  I vaguely recall I had mentioned this earlier... but anyway.
  Indeed I did mention it om 25 Nov 2005.

I know I have the above in an RFC-Editor note, but since you post a new =
rev anyway, I rather would see you fix it.


Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Monday, February 27, 2006 16:45
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;
> Jean-Francois
> Mule; Woundy, Richard
> Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information
> Base for Data-Over-Cable Service Interface Specification Compliant
> CableModem s and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> I incorporated the changes mentioned below in a preliminary
> draft,=20
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.txt>, with the XML version at=20
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.xml>.
>=20
> Your comments are solicited and encouraged; this is the
> version I currently plan to submit on March 3rd if all goes well.
>=20
> I performed all of the same checks (online idnits tool,
> xml2rfc validator tool, and smilint) on this draft version,=20
> and got the same results (basically clean) as performed in=20
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html>.
>=20
> As I edited the current draft, I discovered we needed one
> more update. We "anticipated" outbound LLC filters in the=20
> DOCSIS QoS MIB draft in section 3.3.4; now that the DOCSIS=20
> QoS MIB is published as RFC 4323, the text needed to be=20
> corrected. In addition, I needed to update the reference to=20
> the permanent RFC number, of course.
>=20
> OLD TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet
> just prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but it is=20
> anticipated that
>    the Quality of Service (QoS) additions to the DOCSIS standard
>    [I-D.ietf-ipcdn-qos-mib] may include some outbound LLC filtering
>    requirements.  If so, those filters would be applied as described
>    there.
>=20
> NEW TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet
> just prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but section 3 of the
>    DOCSIS Quality of Service (QoS) MIB, [RFC4323], includes=20
> outbound LLC
>    filtering requirements.
>=20
> -- Rich
>=20
> -----Original Message-----
> From: Woundy, Richard
> Sent: Monday, February 27, 2006 12:34 AM
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> Jean-Francois Mule; Woundy, Richard
> Subject: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information Base for Data-Over-Cable Service Interface=20
> Specification Compliant CableModem s and Cable Modem=20
> Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> This note summarizes the editor and WG chairs' response to
> the IETF Last Call comment received on 12/19/2005 by the IESG=20
> from Brian Hedstrom <b.hedstrom@cablelabs.com> on the ID:=20
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> v2-10.txt.
>=20
> This email response has been previously shared with Brian
> Hedstrom and we believe it addresses the comment raised by=20
> him, based on existing product implementation and best common=20
> practices from DOCSIS cable operators.
>=20
> In short, we propose to address Brian's comment by adding
> clarification text in the current IPCDN MIB module to indicate:
>=20
> 1) CM implementations must report the *first* Syslog server
> from the DHCP log server option value if the DHCP option=20
> received by the CM was multi-valued, and
>=20
> 2) CM implementations must report the *active* time server
> from the DHCP time server option value if the DHCP option=20
> received by the CM was multi-valued.
>=20
> Let us know if there are any objections to this response by
> Friday March 3rd 5pm Eastern Time (note that the draft=20
> submission cut-off is Monday March 6th 9am ET). If there are=20
> no objections by this time, we will post the revision to the=20
> draft including only these two modifications and minimal=20
> editorial changes e.g. draft version, posting date, revision=20
> date, etc. Then we believe the IETF Last Call process will be=20
> complete, and we will assume the draft can proceed=20
> immediately to IESG evaluation and approval.
>=20
> Rich and Jean-Fran=E7ois Mul=E9
> --- Rich as Editor of the IPCDN ID and both as IPCDN co-chairs
> ---
>=20
> In introduction, the chairs would like to note the following:
>    a) the IPCDN Internet-Draft in question is an update to
> RFC 2669 (the original IPCDN Cable Device MIB) published in=20
> August 1999. The multi-valued options in DHCP are specified=20
> in RFC 2132 which was published prior to RFC2669 in March=20
> 1997, so the current MIB module restrictions for a single=20
> time server and single log (Syslog) server have been around=20
> for over six years, without any WG, vendor or cable modem=20
> operator comments raised during the updating of the RFC based=20
> on the inability for the MIB objects to reflect multi-value options;
>    b) existing implementations and current DOCSIS cable modem=20
> compliance indicate that most manufacturers do effectively=20
> treat the log server options as single valued;
>    c) most operators do rely on various, multiple mechanisms=20
> to provide server redundancy for Syslog servers; and
>    d) existing implementations and current DOCSIS (1.1 and=20
> 2.0) cable modem compliance indicate that most manufacturers=20
> do effectively treat the time server options as multi valued=20
> for the purpose of determining a functional time server for a=20
> single boot-time time synchronization event, per DOCSIS RFI=20
> 1.1 section 9.2.7 and DOCSIS RFI 2.0 section 11.2.7.
>=20
> Furthermore, the Syslog server MIB object is read-writeable
> meaning that, after the CM completes DHCP, the CM may=20
> download a configuration file from the operator's OSS systems=20
> containing SNMP 'Set' commands for that MIB object. This=20
> provides cable operators additional flexibility and is yet=20
> another indicator that best common practice is to use a=20
> single value to set that option in the CM configuration files.
>=20
> This being said, we thank Brian for his comment and we
> believe that the comment should be taken into account to add=20
> clarification text in the 2 relevant MIB objects so that new=20
> implementers faced with the same questions know how to=20
> proceed for DOCSIS 1.x and 2.0. Even though we are not aware=20
> of inconsistent implementations, or the practical needs to=20
> address this concern, this may guarantee "more" consistency=20
> in the future. As for future versions of DOCSIS, operator=20
> guidance should be requested on these topics.
>=20
> --- Brian's comment:
> See full details at:
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01837.html
>=20
> In summary, the comment raises a question on the support of
> multiple Syslog servers in the CM due to the limitations of=20
> docsDevEvSyslogAddress object when the CM is provided with=20
> multiple server values in DHCP Option 7.
>=20
> As Rich pointed out in:
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01838.html
> the latest DOCSIS RFI specification available at:=20
> <http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-05
> 1209.pdf>,
> in annex D.1.1, and RFC 2132, defines 5 DHCP options. Three=20
> of out the five standard DHCP options specified are allowed=20
> to be multi-valued:
> * Option code 3 (Router Option)
> * Option code 4 (Time Server Option) -> docsDevServerTimeAddress
> * Option code 7 (Log Server Option)  -> docsDevEvSyslogAddress
>=20
> Note that the Router Option is not referenced by any MIB
> object in this MIB module.
>=20
> Based on the rationale explained above in introduction of
> this email, we propose to add the following text to the=20
> following objects in
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
v2-10.txt:

- docsDevServerTimeAddress:
NEW TEXT:
   docsDevServerTimeAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "The Internet address of the RFC 868 Time server
                as provided by DHCP option 4.=20

                Note that if multiple values are provided to the=20
                CM in DHCP option 4, the value of this MIB object
                MUST be the Time server address from which the Time
                of Day reference was acquired based on the DOCSIS=20
                RFI specification. During the period of time where
                the Time of Day have not been acquired, the Time=20
                server address reported by the CM may report the=20
                first address value in the DHCP option value or the
                last server address the CM attempted to get the Time
                of day value.

                Returns the zero length octet string if the time server
                IP address is not provisioned."
           REFERENCE
               "DOCSIS RFI 1.1 Specification, Section 9.2.7. and
                DOCSIS RFI 2.0 Specification, Section 11.2.7."
           ::=3D { docsDevServer 9 }


- docsDevEvSyslogAddress:
NEW TEXT:
   docsDevEvSyslogAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-write
           STATUS      current
           DESCRIPTION
               "The Internet address of the Syslog server as provided by
                DHCP option 7 or set via SNMP management.  If the
                address of the server is set to any of the zero length
                string, the 0.0.0.0 IPv4 address or the 0: IPv6 address,
                Syslog transmission is inhibited. =20

                Note that if multiple values are provided to the CM in
                DHCP option 7, the value of this MIB object MUST be the
                first Syslog server address received.

                By default at agent boot, this object returns the zero
                length string."
           ::=3D { docsDevEvent 10 }

We believe this addresses the comment by indicating how current =
implementations deal with this situation.
------------------------------------------------------------------

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Thu Mar 02 04:59:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEkah-0001vS-Fi; Thu, 02 Mar 2006 04:59:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEkag-0001uu-Ga
	for ipcdn@ietf.org; Thu, 02 Mar 2006 04:59:22 -0500
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEkae-0006o9-Rd
	for ipcdn@ietf.org; Thu, 02 Mar 2006 04:59:22 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k229xBBY025441; 
	Thu, 2 Mar 2006 03:59:12 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <DVB4YVTF>; Thu, 2 Mar 2006 10:59:09 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15509721D26@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, ipcdn@ietf.org
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information B
	ase for Data-Over-Cable Service Interface Specification Compliant
	CableMo
	dem s and Cable Modem Termination Systems' to Proposed Standard
Date: Thu, 2 Mar 2006 10:59:09 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ihemail2.lucent.com id
	k229xBBY025441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a630332fa112280ecc4c4186b5c9ea83
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	Brian Hedstrom <B.Hedstrom@cablelabs.com>, rdroms@cisco.com
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

looks good to me.

Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Thursday, March 02, 2006 03:03
> To: Wijnen, Bert (Bert); ipcdn@ietf.org
> Cc: Brian Hedstrom; rdroms@cisco.com; Jean-Francois Mule; Woundy,
> Richard
> Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information
> Base for Data-Over-Cable Service Interface Specification Compliant
> CableModem s and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> Thanks, Bert. So here is the resulting change in my private=20
> copy of the draft (to be submitted on Friday).
>=20
> OLD TEXT
>=20
>            DESCRIPTION
>                "This is the MIB Module for DOCSIS-compliant=20
> cable modems
>                 and cable-modem termination systems.
>=20
>                 Copyright (C) The Internet Society (2006). The initial
>                 version of this MIB module was published in RFC XXXX;
>                 for full legal notices see the RFC itself.
>                 Supplementary information may be available at:
>                 http://www.ietf.org/copyrights/ianamib.html."
>=20
> NEW TEXT
>=20
>            DESCRIPTION
>                "This is the MIB Module for DOCSIS-compliant=20
> cable modems
>                 and cable-modem termination systems.
>=20
>                 Copyright (C) The Internet Society (2006).=20
> This version
>                 of this MIB module was published in RFC XXXX; for full
>                 legal notices see the RFC itself."
>=20
> In addition, my copy of the draft needed a similar=20
> modification as discussed for the DOCSIS RF MIB per=20
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01870.html>.
>=20
> OLD TEXT
>=20
> 2.4.  DOCSIS or Data-Over-Cable Service Interface Specification
>=20
>    "Data-Over-Cable Service Interface Specification".  A term=20
> referring
>    to the ITU-T J.112 [ITU-T_J.112] Annex B standard for cable modem
>    systems.  [RFI1.0] [RFI1.1] [RFI2.0]
>=20
> NEW TEXT
>=20
> 2.4.  DOCSIS or Data-Over-Cable Service Interface Specification
>=20
>    "Data-Over-Cable Service Interface Specification".  A term=20
> referring
>    to the ITU-T Recommendation J.112 [ITU-T_J.112] Annex B=20
> standard for
>    cable modem systems.  [RFI1.0] [RFI1.1] [RFI2.0]
>=20
> -- Rich
>=20
> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
> Sent: Wednesday, March 01, 2006 10:55 AM
> To: Woundy, Richard; ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> Jean-Francois Mule
> Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information Base for Data-Over-Cable Service Interface=20
> Specification Compliant CableModem s and Cable Modem=20
> Termination Systems' to Proposed Standard
>=20
>=20
> A nit:
>=20
> The DESCRIPTION clause of the MODULE-IDENTITY states:
>            DESCRIPTION
>                "This is the MIB Module for DOCSIS-compliant=20
> cable modems
>                 and cable-modem termination systems.
>=20
>                 Copyright (C) The Internet Society (2006). The initial
>                 version of this MIB module was published in RFC XXXX;
>                 for full legal notices see the RFC itself.
>                 Supplementary information may be available at:
>                 http://www.ietf.org/copyrights/ianamib.html."
>=20
> - I would change "The initial version" to "This version".=20
>   Because we really want people to look at this RFC which has this
>   version and not the initial version of RFC2669.
> - I would remove the last sentence:
>                 Supplementary information may be available at:
>                 http://www.ietf.org/copyrights/ianamib.html.
>   because this is a standalone MIB module and is not maintained
>   by IANA at all. So IANA notices on copyrights do not apply I think.
>   I vaguely recall I had mentioned this earlier... but anyway.
>   Indeed I did mention it om 25 Nov 2005.
>=20
> I know I have the above in an RFC-Editor note, but since you=20
> post a new rev anyway, I rather would see you fix it.
>=20
>=20
> Bert
>=20
> > -----Original Message-----
> > From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> > Sent: Monday, February 27, 2006 16:45
> > To: ipcdn@ietf.org
> > Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;
> > Jean-Francois
> > Mule; Woundy, Richard
> > Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> > Information
> > Base for Data-Over-Cable Service Interface Specification Compliant
> > CableModem s and Cable Modem Termination Systems' to=20
> Proposed Standard
> >=20
> >=20
> > Folks,
> >=20
> > I incorporated the changes mentioned below in a preliminary
> > draft,=20
> > <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> > proposed.txt>, with the XML version at=20
> > <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> > proposed.xml>.
> >=20
> > Your comments are solicited and encouraged; this is the
> > version I currently plan to submit on March 3rd if all goes well.
> >=20
> > I performed all of the same checks (online idnits tool,
> > xml2rfc validator tool, and smilint) on this draft version,=20
> > and got the same results (basically clean) as performed in=20
> > <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html>.
> >=20
> > As I edited the current draft, I discovered we needed one
> > more update. We "anticipated" outbound LLC filters in the=20
> > DOCSIS QoS MIB draft in section 3.3.4; now that the DOCSIS=20
> > QoS MIB is published as RFC 4323, the text needed to be=20
> > corrected. In addition, I needed to update the reference to=20
> > the permanent RFC number, of course.
> >=20
> > OLD TEXT
> >=20
> >    Lastly, any outbound LLC filters are applied to the packet
> > just prior
> >    to it being emitted on the appropriate interface.  This=20
> MIB module
> >    does not specify any outbound LLC filters, but it is=20
> > anticipated that
> >    the Quality of Service (QoS) additions to the DOCSIS standard
> >    [I-D.ietf-ipcdn-qos-mib] may include some outbound LLC filtering
> >    requirements.  If so, those filters would be applied as described
> >    there.
> >=20
> > NEW TEXT
> >=20
> >    Lastly, any outbound LLC filters are applied to the packet
> > just prior
> >    to it being emitted on the appropriate interface.  This=20
> MIB module
> >    does not specify any outbound LLC filters, but section 3 of the
> >    DOCSIS Quality of Service (QoS) MIB, [RFC4323], includes=20
> > outbound LLC
> >    filtering requirements.
> >=20
> > -- Rich
> >=20
> > -----Original Message-----
> > From: Woundy, Richard
> > Sent: Monday, February 27, 2006 12:34 AM
> > To: ipcdn@ietf.org
> > Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> > Jean-Francois Mule; Woundy, Richard
> > Subject: Re: [ipcdn] Last Call: 'Cable Device Management=20
> > Information Base for Data-Over-Cable Service Interface=20
> > Specification Compliant CableModem s and Cable Modem=20
> > Termination Systems' to Proposed Standard
> >=20
> >=20
> > Folks,
> >=20
> > This note summarizes the editor and WG chairs' response to
> > the IETF Last Call comment received on 12/19/2005 by the IESG=20
> > from Brian Hedstrom <b.hedstrom@cablelabs.com> on the ID:=20
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> > v2-10.txt.
> >=20
> > This email response has been previously shared with Brian
> > Hedstrom and we believe it addresses the comment raised by=20
> > him, based on existing product implementation and best common=20
> > practices from DOCSIS cable operators.
> >=20
> > In short, we propose to address Brian's comment by adding
> > clarification text in the current IPCDN MIB module to indicate:
> >=20
> > 1) CM implementations must report the *first* Syslog server
> > from the DHCP log server option value if the DHCP option=20
> > received by the CM was multi-valued, and
> >=20
> > 2) CM implementations must report the *active* time server
> > from the DHCP time server option value if the DHCP option=20
> > received by the CM was multi-valued.
> >=20
> > Let us know if there are any objections to this response by
> > Friday March 3rd 5pm Eastern Time (note that the draft=20
> > submission cut-off is Monday March 6th 9am ET). If there are=20
> > no objections by this time, we will post the revision to the=20
> > draft including only these two modifications and minimal=20
> > editorial changes e.g. draft version, posting date, revision=20
> > date, etc. Then we believe the IETF Last Call process will be=20
> > complete, and we will assume the draft can proceed=20
> > immediately to IESG evaluation and approval.
> >=20
> > Rich and Jean-Fran=E7ois Mul=E9
> > --- Rich as Editor of the IPCDN ID and both as IPCDN co-chairs
> > ---
> >=20
> > In introduction, the chairs would like to note the following:
> >    a) the IPCDN Internet-Draft in question is an update to
> > RFC 2669 (the original IPCDN Cable Device MIB) published in=20
> > August 1999. The multi-valued options in DHCP are specified=20
> > in RFC 2132 which was published prior to RFC2669 in March=20
> > 1997, so the current MIB module restrictions for a single=20
> > time server and single log (Syslog) server have been around=20
> > for over six years, without any WG, vendor or cable modem=20
> > operator comments raised during the updating of the RFC based=20
> > on the inability for the MIB objects to reflect multi-value options;
> >    b) existing implementations and current DOCSIS cable modem=20
> > compliance indicate that most manufacturers do effectively=20
> > treat the log server options as single valued;
> >    c) most operators do rely on various, multiple mechanisms=20
> > to provide server redundancy for Syslog servers; and
> >    d) existing implementations and current DOCSIS (1.1 and=20
> > 2.0) cable modem compliance indicate that most manufacturers=20
> > do effectively treat the time server options as multi valued=20
> > for the purpose of determining a functional time server for a=20
> > single boot-time time synchronization event, per DOCSIS RFI=20
> > 1.1 section 9.2.7 and DOCSIS RFI 2.0 section 11.2.7.
> >=20
> > Furthermore, the Syslog server MIB object is read-writeable
> > meaning that, after the CM completes DHCP, the CM may=20
> > download a configuration file from the operator's OSS systems=20
> > containing SNMP 'Set' commands for that MIB object. This=20
> > provides cable operators additional flexibility and is yet=20
> > another indicator that best common practice is to use a=20
> > single value to set that option in the CM configuration files.
> >=20
> > This being said, we thank Brian for his comment and we
> > believe that the comment should be taken into account to add=20
> > clarification text in the 2 relevant MIB objects so that new=20
> > implementers faced with the same questions know how to=20
> > proceed for DOCSIS 1.x and 2.0. Even though we are not aware=20
> > of inconsistent implementations, or the practical needs to=20
> > address this concern, this may guarantee "more" consistency=20
> > in the future. As for future versions of DOCSIS, operator=20
> > guidance should be requested on these topics.
> >=20
> > --- Brian's comment:
> > See full details at:
> > http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01837.html
> >=20
> > In summary, the comment raises a question on the support of
> > multiple Syslog servers in the CM due to the limitations of=20
> > docsDevEvSyslogAddress object when the CM is provided with=20
> > multiple server values in DHCP Option 7.
> >=20
> > As Rich pointed out in:
> > http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01838.html
> > the latest DOCSIS RFI specification available at:=20
> > <http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-05
> > 1209.pdf>,
> > in annex D.1.1, and RFC 2132, defines 5 DHCP options. Three=20
> > of out the five standard DHCP options specified are allowed=20
> > to be multi-valued:
> > * Option code 3 (Router Option)
> > * Option code 4 (Time Server Option) -> docsDevServerTimeAddress
> > * Option code 7 (Log Server Option)  -> docsDevEvSyslogAddress
> >=20
> > Note that the Router Option is not referenced by any MIB
> > object in this MIB module.
> >=20
> > Based on the rationale explained above in introduction of
> > this email, we propose to add the following text to the=20
> > following objects in
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> v2-10.txt:
>=20
> - docsDevServerTimeAddress:
> NEW TEXT:
>    docsDevServerTimeAddress OBJECT-TYPE
>            SYNTAX      InetAddress
>            MAX-ACCESS  read-only
>            STATUS      current
>            DESCRIPTION
>                "The Internet address of the RFC 868 Time server
>                 as provided by DHCP option 4.=20
>=20
>                 Note that if multiple values are provided to the=20
>                 CM in DHCP option 4, the value of this MIB object
>                 MUST be the Time server address from which the Time
>                 of Day reference was acquired based on the DOCSIS=20
>                 RFI specification. During the period of time where
>                 the Time of Day have not been acquired, the Time=20
>                 server address reported by the CM may report the=20
>                 first address value in the DHCP option value or the
>                 last server address the CM attempted to get the Time
>                 of day value.
>=20
>                 Returns the zero length octet string if the=20
> time server
>                 IP address is not provisioned."
>            REFERENCE
>                "DOCSIS RFI 1.1 Specification, Section 9.2.7. and
>                 DOCSIS RFI 2.0 Specification, Section 11.2.7."
>            ::=3D { docsDevServer 9 }
>=20
>=20
> - docsDevEvSyslogAddress:
> NEW TEXT:
>    docsDevEvSyslogAddress OBJECT-TYPE
>            SYNTAX      InetAddress
>            MAX-ACCESS  read-write
>            STATUS      current
>            DESCRIPTION
>                "The Internet address of the Syslog server as=20
> provided by
>                 DHCP option 7 or set via SNMP management.  If the
>                 address of the server is set to any of the zero length
>                 string, the 0.0.0.0 IPv4 address or the 0:=20
> IPv6 address,
>                 Syslog transmission is inhibited. =20
>=20
>                 Note that if multiple values are provided to the CM in
>                 DHCP option 7, the value of this MIB object=20
> MUST be the
>                 first Syslog server address received.
>=20
>                 By default at agent boot, this object returns the zero
>                 length string."
>            ::=3D { docsDevEvent 10 }
>=20
> We believe this addresses the comment by indicating how=20
> current implementations deal with this situation.
> ------------------------------------------------------------------
>=20

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Thu Mar 02 15:25:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEuMv-00083u-CI; Thu, 02 Mar 2006 15:25:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEuMu-00083k-EL
	for ipcdn@ietf.org; Thu, 02 Mar 2006 15:25:48 -0500
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEuMt-00066S-6s
	for ipcdn@ietf.org; Thu, 02 Mar 2006 15:25:48 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k22KPjve019460
	for <ipcdn@ietf.org>; Thu, 2 Mar 2006 14:25:45 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <DVB4ZD3L>; Thu, 2 Mar 2006 21:25:44 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15509721FA4@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ipcdn (E-mail)" <ipcdn@ietf.org>
Date: Thu, 2 Mar 2006 21:25:43 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [ipcdn] FW: draft-ietf-ipcdn-docs-rfmibv2-14.txt approved by IESG
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Congrats to WG and specifically to authors/editors.

Formal announcement will follow from IESG
secretariat in a few days.

Bert

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Fri Mar 03 12:02:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FFDfX-00033X-TV; Fri, 03 Mar 2006 12:02:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FFDfW-00033A-4C
	for ipcdn@ietf.org; Fri, 03 Mar 2006 12:02:18 -0500
Received: from pacdcoavas09.cable.comcast.com ([208.17.33.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FFDfU-0004rD-HK
	for ipcdn@ietf.org; Fri, 03 Mar 2006 12:02:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information Base
	for Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed Standard
Date: Fri, 3 Mar 2006 12:01:52 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF77C@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [ipcdn] Last Call: 'Cable Device Management Information Base
	for Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed
	Standard
Thread-Index: AcY9SIkvyokh+YLGQZ6gMOgOLnAxMgAU8u7wAFHdtMA=
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <ipcdn@ietf.org>
X-OriginalArrivalTime: 03 Mar 2006 17:01:53.0135 (UTC)
	FILETIME=[2B95EFF0:01C63EE4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2c12be3f3a8d57895fb9c003e1517c01
Cc: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
	Jean-Francois Mule <jf.mule@cablelabs.com>, "Woundy,
	Richard" <Richard_Woundy@cable.comcast.com>,
	Brian Hedstrom <B.Hedstrom@cablelabs.com>, rdroms@cisco.com
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

In the absence of any other public feedback, here is a copy of what I =
plan to submit today (to internet-drafts) at 5pm ET.

<http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11.txt>
<http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11.xml>

-- Rich

-----Original Message-----
From: Woundy, Richard=20
Sent: Wednesday, March 01, 2006 9:03 PM
To: Wijnen, Bert (Bert); ipcdn@ietf.org
Cc: Brian Hedstrom; rdroms@cisco.com; Jean-Francois Mule; Woundy, =
Richard
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information =
Base for Data-Over-Cable Service Interface Specification Compliant =
CableModem s and Cable Modem Termination Systems' to Proposed Standard


Thanks, Bert. So here is the resulting change in my private copy of the =
draft (to be submitted on Friday).

OLD TEXT

           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html."

NEW TEXT

           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). This version
                of this MIB module was published in RFC XXXX; for full
                legal notices see the RFC itself."

In addition, my copy of the draft needed a similar modification as =
discussed for the DOCSIS RF MIB per =
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01870.html>.

OLD TEXT

2.4.  DOCSIS or Data-Over-Cable Service Interface Specification

   "Data-Over-Cable Service Interface Specification".  A term referring
   to the ITU-T J.112 [ITU-T_J.112] Annex B standard for cable modem
   systems.  [RFI1.0] [RFI1.1] [RFI2.0]

NEW TEXT

2.4.  DOCSIS or Data-Over-Cable Service Interface Specification

   "Data-Over-Cable Service Interface Specification".  A term referring
   to the ITU-T Recommendation J.112 [ITU-T_J.112] Annex B standard for
   cable modem systems.  [RFI1.0] [RFI1.1] [RFI2.0]

-- Rich

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
Sent: Wednesday, March 01, 2006 10:55 AM
To: Woundy, Richard; ipcdn@ietf.org
Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com; Jean-Francois =
Mule
Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management Information =
Base for Data-Over-Cable Service Interface Specification Compliant =
CableModem s and Cable Modem Termination Systems' to Proposed Standard


A nit:

The DESCRIPTION clause of the MODULE-IDENTITY states:
           DESCRIPTION
               "This is the MIB Module for DOCSIS-compliant cable modems
                and cable-modem termination systems.

                Copyright (C) The Internet Society (2006). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html."

- I would change "The initial version" to "This version".=20
  Because we really want people to look at this RFC which has this
  version and not the initial version of RFC2669.
- I would remove the last sentence:
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html.
  because this is a standalone MIB module and is not maintained
  by IANA at all. So IANA notices on copyrights do not apply I think.
  I vaguely recall I had mentioned this earlier... but anyway.
  Indeed I did mention it om 25 Nov 2005.

I know I have the above in an RFC-Editor note, but since you post a new =
rev anyway, I rather would see you fix it.


Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Monday, February 27, 2006 16:45
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;=20
> Jean-Francois Mule; Woundy, Richard
> Subject: RE: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information
> Base for Data-Over-Cable Service Interface Specification Compliant
> CableModem s and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> I incorporated the changes mentioned below in a preliminary draft,
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.txt>, with the XML version at=20
> <http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-11-
> proposed.xml>.
>=20
> Your comments are solicited and encouraged; this is the version I=20
> currently plan to submit on March 3rd if all goes well.
>=20
> I performed all of the same checks (online idnits tool, xml2rfc=20
> validator tool, and smilint) on this draft version, and got the same=20
> results (basically clean) as performed in=20
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html>.
>=20
> As I edited the current draft, I discovered we needed one more update. =

> We "anticipated" outbound LLC filters in the DOCSIS QoS MIB draft in=20
> section 3.3.4; now that the DOCSIS QoS MIB is published as RFC 4323,=20
> the text needed to be corrected. In addition, I needed to update the=20
> reference to the permanent RFC number, of course.
>=20
> OLD TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet just=20
> prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but it is
> anticipated that
>    the Quality of Service (QoS) additions to the DOCSIS standard
>    [I-D.ietf-ipcdn-qos-mib] may include some outbound LLC filtering
>    requirements.  If so, those filters would be applied as described
>    there.
>=20
> NEW TEXT
>=20
>    Lastly, any outbound LLC filters are applied to the packet just=20
> prior
>    to it being emitted on the appropriate interface.  This MIB module
>    does not specify any outbound LLC filters, but section 3 of the
>    DOCSIS Quality of Service (QoS) MIB, [RFC4323], includes
> outbound LLC
>    filtering requirements.
>=20
> -- Rich
>=20
> -----Original Message-----
> From: Woundy, Richard
> Sent: Monday, February 27, 2006 12:34 AM
> To: ipcdn@ietf.org
> Cc: Brian Hedstrom; Wijnen, Bert (Bert); rdroms@cisco.com;
> Jean-Francois Mule; Woundy, Richard
> Subject: Re: [ipcdn] Last Call: 'Cable Device Management=20
> Information Base for Data-Over-Cable Service Interface=20
> Specification Compliant CableModem s and Cable Modem=20
> Termination Systems' to Proposed Standard
>=20
>=20
> Folks,
>=20
> This note summarizes the editor and WG chairs' response to the IETF=20
> Last Call comment received on 12/19/2005 by the IESG from Brian=20
> Hedstrom <b.hedstrom@cablelabs.com> on the ID:=20
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> v2-10.txt.
>=20
> This email response has been previously shared with Brian Hedstrom and =

> we believe it addresses the comment raised by him, based on existing=20
> product implementation and best common practices from DOCSIS cable=20
> operators.
>=20
> In short, we propose to address Brian's comment by adding=20
> clarification text in the current IPCDN MIB module to indicate:
>=20
> 1) CM implementations must report the *first* Syslog server from the=20
> DHCP log server option value if the DHCP option received by the CM was =

> multi-valued, and
>=20
> 2) CM implementations must report the *active* time server from the=20
> DHCP time server option value if the DHCP option received by the CM=20
> was multi-valued.
>=20
> Let us know if there are any objections to this response by Friday=20
> March 3rd 5pm Eastern Time (note that the draft submission cut-off is=20
> Monday March 6th 9am ET). If there are no objections by this time, we=20
> will post the revision to the draft including only these two=20
> modifications and minimal editorial changes e.g. draft version,=20
> posting date, revision date, etc. Then we believe the IETF Last Call=20
> process will be complete, and we will assume the draft can proceed
> immediately to IESG evaluation and approval.
>=20
> Rich and Jean-Fran=E7ois Mul=E9
> --- Rich as Editor of the IPCDN ID and both as IPCDN co-chairs
> ---
>=20
> In introduction, the chairs would like to note the following:
>    a) the IPCDN Internet-Draft in question is an update to RFC 2669=20
> (the original IPCDN Cable Device MIB) published in August 1999. The=20
> multi-valued options in DHCP are specified in RFC 2132 which was=20
> published prior to RFC2669 in March 1997, so the current MIB module=20
> restrictions for a single time server and single log (Syslog) server=20
> have been around for over six years, without any WG, vendor or cable=20
> modem operator comments raised during the updating of the RFC based
> on the inability for the MIB objects to reflect multi-value options;
>    b) existing implementations and current DOCSIS cable modem=20
> compliance indicate that most manufacturers do effectively=20
> treat the log server options as single valued;
>    c) most operators do rely on various, multiple mechanisms=20
> to provide server redundancy for Syslog servers; and
>    d) existing implementations and current DOCSIS (1.1 and=20
> 2.0) cable modem compliance indicate that most manufacturers=20
> do effectively treat the time server options as multi valued=20
> for the purpose of determining a functional time server for a=20
> single boot-time time synchronization event, per DOCSIS RFI=20
> 1.1 section 9.2.7 and DOCSIS RFI 2.0 section 11.2.7.
>=20
> Furthermore, the Syslog server MIB object is read-writeable meaning=20
> that, after the CM completes DHCP, the CM may download a configuration =

> file from the operator's OSS systems containing SNMP 'Set' commands=20
> for that MIB object. This provides cable operators additional=20
> flexibility and is yet another indicator that best common practice is=20
> to use a single value to set that option in the CM configuration=20
> files.
>=20
> This being said, we thank Brian for his comment and we believe that=20
> the comment should be taken into account to add clarification text in=20
> the 2 relevant MIB objects so that new implementers faced with the=20
> same questions know how to proceed for DOCSIS 1.x and 2.0. Even though =

> we are not aware of inconsistent implementations, or the practical=20
> needs to address this concern, this may guarantee "more" consistency
> in the future. As for future versions of DOCSIS, operator=20
> guidance should be requested on these topics.
>=20
> --- Brian's comment:
> See full details at:=20
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01837.html
>=20
> In summary, the comment raises a question on the support of multiple=20
> Syslog servers in the CM due to the limitations of=20
> docsDevEvSyslogAddress object when the CM is provided with multiple=20
> server values in DHCP Option 7.
>=20
> As Rich pointed out in:=20
> http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01838.html
> the latest DOCSIS RFI specification available at:
> <http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-05
> 1209.pdf>,
> in annex D.1.1, and RFC 2132, defines 5 DHCP options. Three=20
> of out the five standard DHCP options specified are allowed=20
> to be multi-valued:
> * Option code 3 (Router Option)
> * Option code 4 (Time Server Option) -> docsDevServerTimeAddress
> * Option code 7 (Log Server Option)  -> docsDevEvSyslogAddress
>=20
> Note that the Router Option is not referenced by any MIB object in=20
> this MIB module.
>=20
> Based on the rationale explained above in introduction of this email,=20
> we propose to add the following text to the following objects in
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
v2-10.txt:

- docsDevServerTimeAddress:
NEW TEXT:
   docsDevServerTimeAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "The Internet address of the RFC 868 Time server
                as provided by DHCP option 4.=20

                Note that if multiple values are provided to the=20
                CM in DHCP option 4, the value of this MIB object
                MUST be the Time server address from which the Time
                of Day reference was acquired based on the DOCSIS=20
                RFI specification. During the period of time where
                the Time of Day have not been acquired, the Time=20
                server address reported by the CM may report the=20
                first address value in the DHCP option value or the
                last server address the CM attempted to get the Time
                of day value.

                Returns the zero length octet string if the time server
                IP address is not provisioned."
           REFERENCE
               "DOCSIS RFI 1.1 Specification, Section 9.2.7. and
                DOCSIS RFI 2.0 Specification, Section 11.2.7."
           ::=3D { docsDevServer 9 }


- docsDevEvSyslogAddress:
NEW TEXT:
   docsDevEvSyslogAddress OBJECT-TYPE
           SYNTAX      InetAddress
           MAX-ACCESS  read-write
           STATUS      current
           DESCRIPTION
               "The Internet address of the Syslog server as provided by
                DHCP option 7 or set via SNMP management.  If the
                address of the server is set to any of the zero length
                string, the 0.0.0.0 IPv4 address or the 0: IPv6 address,
                Syslog transmission is inhibited. =20

                Note that if multiple values are provided to the CM in
                DHCP option 7, the value of this MIB object MUST be the
                first Syslog server address received.

                By default at agent boot, this object returns the zero
                length string."
           ::=3D { docsDevEvent 10 }

We believe this addresses the comment by indicating how current =
implementations deal with this situation.
------------------------------------------------------------------

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Mon Mar 06 02:50:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGATl-0006Rn-IT; Mon, 06 Mar 2006 02:50:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGATj-0006QP-S6; Mon, 06 Mar 2006 02:50:03 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGATh-0003e0-JJ; Mon, 06 Mar 2006 02:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k267o1BX007524
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 6 Mar 2006 07:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FGATh-0008KC-CR; Mon, 06 Mar 2006 02:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FGATh-0008KC-CR@stiedprstage1.ietf.org>
Date: Mon, 06 Mar 2006 02:50:01 -0500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over Cable Data Network Working Group of the IETF.

	Title		: Cable Device Management Information Base for 
                          Data-Over-Cable Service Interface 
                          Specification Compliant Cable Modems and 
                          Cable Modem Termination Systems
	Author(s)	: R. Woundy, K. Marez
	Filename	: draft-ietf-ipcdn-device-mibv2-11.txt
	Pages		: 93
	Date		: 2006-3-5
	
This memo is a revision of the standards track RFC 2669.  Please see
"Revision Descriptions" below for a description of changes.  This
document obsoletes RFC 2669.

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for SNMP-
based management of DOCSIS-compliant Cable Modems and Cable Modem
Termination Systems.

This memo is a product of the IPCDN working group within the Internet
Engineering Task Force.  Comments are solicited and should be
addressed to the working group's mailing list at ipcdn@ietf.org
and/or the author.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ipcdn-device-mibv2-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-3-5183046.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ipcdn-device-mibv2-11.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-3-5183046.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--NextPart--




From ipcdn-bounces@ietf.org Mon Mar 06 10:19:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGHUD-0000Qi-Lf; Mon, 06 Mar 2006 10:19:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FGHUB-0000L2-Vr
	for ipcdn@ietf.org; Mon, 06 Mar 2006 10:19:00 -0500
Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]
	helo=cable.comcast.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGHUB-0005i3-ID
	for ipcdn@ietf.org; Mon, 06 Mar 2006 10:18:59 -0500
Received: from ([10.52.116.30])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-TDCH7.17525935;
	Mon, 06 Mar 2006 10:18:30 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 6 Mar 2006 10:18:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
Date: Mon, 6 Mar 2006 10:18:29 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF793@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
Thread-Index: AcZA8rCXWJx4TCByTmGmg1daZOjwZwAPjFLw
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <ipcdn@ietf.org>
X-OriginalArrivalTime: 06 Mar 2006 15:18:29.0859 (UTC)
	FILETIME=[39626330:01C64131]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Folks,

This is the draft version I promised to post on Friday at 5pm ET, per
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01876.html>.

-- Rich

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Monday, March 06, 2006 2:50 AM
To: i-d-announce@ietf.org
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt=20


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the IP over Cable Data Network
Working Group of the IETF.

	Title		: Cable Device Management Information Base for=20
                          Data-Over-Cable Service Interface=20
                          Specification Compliant Cable Modems and=20
                          Cable Modem Termination Systems
	Author(s)	: R. Woundy, K. Marez
	Filename	: draft-ietf-ipcdn-device-mibv2-11.txt
	Pages		: 93
	Date		: 2006-3-5
=09
This memo is a revision of the standards track RFC 2669.  Please see
"Revision Descriptions" below for a description of changes.  This
document obsoletes RFC 2669.

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In
particular, it defines a basic set of managed objects for SNMP- based
management of DOCSIS-compliant Cable Modems and Cable Modem Termination
Systems.

This memo is a product of the IPCDN working group within the Internet
Engineering Task Force.  Comments are solicited and should be addressed
to the working group's mailing list at ipcdn@ietf.org and/or the author.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message. =20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-ietf-ipcdn-device-mibv2-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
	=09
	=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Mon Mar 06 16:14:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGN1m-0002o2-Qf; Mon, 06 Mar 2006 16:14:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGMeb-0001yd-Ns; Mon, 06 Mar 2006 15:50:05 -0500
Received: from [156.154.16.129] (helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGMeb-0001NE-LW; Mon, 06 Mar 2006 15:50:05 -0500
Received: from [156.154.24.129] (helo=oak.neustar.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FGMeY-0002v2-CX; Mon, 06 Mar 2006 15:50:05 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k26Ko1BX024361
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 6 Mar 2006 20:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FGMeX-00055c-TI; Mon, 06 Mar 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FGMeX-00055c-TI@stiedprstage1.ietf.org>
Date: Mon, 06 Mar 2006 15:50:01 -0500
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-signaling-10.txt 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over Cable Data Network Working Group of the IETF.

	Title		: Network-Based Call Signaling (NCS) Signaling 
                          MIB for PacketCable and IPCablecom 
                          Multimedia Terminal Adapters (MTAs)
	Author(s)	: G. Beacham, et al.
	Filename	: draft-ietf-ipcdn-pktc-signaling-10.txt
	Pages		: 69
	Date		: 2006-3-6
	
This memo defines a portion of the Management Information Base (MIB) 
for use with network management protocols in the Internet community. 
In particular, it provides a common data and format representation 
for PacketCable and IPCablecom compliant Multimedia Terminal Adapter 
devices. 
    
This memo specifies a MIB module in a manner that is compliant to 
the SNMP SMIv2.  The set of objects are consistent with the SNMP 
framework and existing SNMP standards. 
    
This memo specifies a MIB module in a manner that is compliant to 
the SNMP SMIv2.  The set of objects are consistent with the SNMP 
framework and existing SNMP standards.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ipcdn-pktc-signaling-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-pktc-signaling-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-3-6103631.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipcdn-pktc-signaling-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ipcdn-pktc-signaling-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-3-6103631.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--NextPart--




From ipcdn-bounces@ietf.org Mon Mar 06 16:13:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGN19-0002Pr-LH; Mon, 06 Mar 2006 16:13:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGN18-0002Pc-U4; Mon, 06 Mar 2006 16:13:22 -0500
Received: from [156.154.16.129] (helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FGMJw-0000I7-Iw; Mon, 06 Mar 2006 15:28:44 -0500
Received: from [156.154.24.129] (helo=oak.neustar.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FGM1A-0002WK-9H; Mon, 06 Mar 2006 15:09:22 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k26K9IBX021423
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 6 Mar 2006 20:09:18 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FGM18-0006gq-4k; Mon, 06 Mar 2006 15:09:18 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1FGM18-0006gq-4k@stiedprstage1.ietf.org>
Date: Mon, 06 Mar 2006 15:09:18 -0500
X-Spam-Score: -5.7 (-----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ipcdn mailing list <ipcdn@ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	ipcdn chair <Richard_Woundy@cable.comcast.com>,
	ipcdn chair <jf.mule@cablelabs.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [ipcdn] Protocol Action: 'Radio Frequency (RF) Interface Management
 Information Base for DOCSIS 2.0 compliant RF interfaces' to Proposed 
 Standard 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

The IESG has approved the following document:

- 'Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 
   compliant RF interfaces '
   <draft-ietf-ipcdn-docs-rfmibv2-14.txt> as a Proposed Standard

This document obsoletes RFC2670.

This document is the product of the IP over Cable Data Network Working Group. 

The IESG contact persons are Bert Wijnen and David Kessens.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt

Technical Summary
 
   This document is a revision of the standards track RFC 2670, and 
   defines a portion of the Management Information Base (MIB) for 
   use with network management protocols in the Internet community. 
   In particular, it defines a set of managed objects for SNMP-based 
   management of the Radio Frequency (RF) interfaces for systems 
   compliant with the Data Over Cable Service Interface Specifications 
   (DOCSIS). 

Working Group Summary 

   The Working Group has consensus to publish this document as a 
   Proposed Standard. 

Protocol Quality 
  
   The MIB module has been reviewed by Randy Presuhn. The overall quality 
   with respect to DOCSIS functionality has been reviewed by many 
   IPCDN technical experts.
   This document has been reviewed for the IESG by Bert Wijnen. 

Note to RFC Editor
 
- In the abstract, pls change
  OLD:
   This document revises and obsoletes RFC 2670.  Please see section 6
   for a description of the changes from RFC 2670.
  NEW:
   This document revises and obsoletes RFC 2670.  Please see section 5.3
   for a description of the changes from RFC 2670.


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Thu Mar 09 00:42:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHDuY-0004jv-R6; Thu, 09 Mar 2006 00:42:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FHDuX-0004jo-Oh
	for ipcdn@ietf.org; Thu, 09 Mar 2006 00:42:05 -0500
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHDuX-0003sz-Dd
	for ipcdn@ietf.org; Thu, 09 Mar 2006 00:42:05 -0500
Received: from ihemail1.lucent.com (h192-11-222-161.lucent.com
	[192.11.222.161])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k295g2rT013941; 
	Wed, 8 Mar 2006 23:42:02 -0600 (CST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k295g1ZP029503; 
	Wed, 8 Mar 2006 23:42:01 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <G3YWVJJ4>; Thu, 9 Mar 2006 06:41:59 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155097B97DD@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, ipcdn@ietf.org
Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
Date: Thu, 9 Mar 2006 06:41:59 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

On IESG agenda for March 16 now.

Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Monday, March 06, 2006 16:18
> To: ipcdn@ietf.org
> Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
> 
> 
> Folks,
> 
> This is the draft version I promised to post on Friday at 5pm ET, per
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01876.html>.
> 
> -- Rich
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> Sent: Monday, March 06, 2006 2:50 AM
> To: i-d-announce@ietf.org
> Cc: ipcdn@ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the IP over Cable 
> Data Network
> Working Group of the IETF.
> 
> 	Title		: Cable Device Management Information Base for 
>                           Data-Over-Cable Service Interface 
>                           Specification Compliant Cable Modems and 
>                           Cable Modem Termination Systems
> 	Author(s)	: R. Woundy, K. Marez
> 	Filename	: draft-ietf-ipcdn-device-mibv2-11.txt
> 	Pages		: 93
> 	Date		: 2006-3-5
> 	
> This memo is a revision of the standards track RFC 2669.  Please see
> "Revision Descriptions" below for a description of changes.  This
> document obsoletes RFC 2669.
> 
> This memo defines a portion of the Management Information 
> Base (MIB) for
> use with network management protocols in the Internet community. In
> particular, it defines a basic set of managed objects for SNMP- based
> management of DOCSIS-compliant Cable Modems and Cable Modem 
> Termination
> Systems.
> 
> This memo is a product of the IPCDN working group within the Internet
> Engineering Task Force.  Comments are solicited and should be 
> addressed
> to the working group's mailing list at ipcdn@ietf.org and/or 
> the author.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mi
bv2-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-ietf-ipcdn-device-mibv2-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Thu Mar 16 15:35:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FJzBp-0004qj-Hx; Thu, 16 Mar 2006 15:35:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FJzBo-0004ng-GD
	for ipcdn@ietf.org; Thu, 16 Mar 2006 15:35:20 -0500
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJzBn-00081J-6w
	for ipcdn@ietf.org; Thu, 16 Mar 2006 15:35:20 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k2GKZHth025737
	for <ipcdn@ietf.org>; Thu, 16 Mar 2006 14:35:18 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <G3YW5LH4>; Thu, 16 Mar 2006 21:35:16 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155098E1CD2@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ipcdn (E-mail)" <ipcdn@ietf.org>
Date: Thu, 16 Mar 2006 21:35:13 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Subject: [ipcdn] IESG has approved: draft-ietf-ipcdn-device-mibv2 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Congrats to the WG and specifically to the authors/editors.

Formal announcement will come from iesg-secretary.

Bert

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Tue Mar 21 16:04:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FLo1s-0004xi-PH; Tue, 21 Mar 2006 16:04:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FLo1r-0004xP-2H; Tue, 21 Mar 2006 16:04:35 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FLo1q-0002SV-RA; Tue, 21 Mar 2006 16:04:35 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k2LL4WvP008578
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 21 Mar 2006 21:04:32 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FLo1o-00076z-Hk; Tue, 21 Mar 2006 16:04:32 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1FLo1o-00076z-Hk@stiedprstage1.ietf.org>
Date: Tue, 21 Mar 2006 16:04:32 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipcdn mailing list <ipcdn@ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	ipcdn chair <Richard_Woundy@cable.comcast.com>,
	ipcdn chair <jf.mule@cablelabs.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [ipcdn] Protocol Action: 'Cable Device Management Information Base 
 for Data-Over-Cable Service Interface Specification Compliant Cable 
 Modems and Cable Modem Termination Systems' to Proposed Standard 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

The IESG has approved the following document:

- 'Cable Device Management Information Base for Data-Over-Cable Service 
   Interface Specification Compliant Cable Modems and Cable Modem Termination 
   Systems '
   <draft-ietf-ipcdn-device-mibv2-11.txt> as a Proposed Standard

This document obsoletes RFC2669.

This document is the product of the IP over Cable Data Network Working Group. 

The IESG contact persons are Bert Wijnen and David Kessens.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt

Technical Summary
 
  This document is a revision of the standards track RFC 2669.
  This document obsoletes RFC 2669.

  This memo defines a portion of the Management Information Base (MIB)
  for use with network management protocols in the Internet community.
  In particular, it defines a basic set of managed objects for SNMP-
  based management of DOCSIS-compliant Cable Modems and Cable Modem
  Termination Systems.

Working Group Summary
 
  The Working Group has consensus to publish this document as a
  Proposed Standard. IETF Last Call comments (to rev 10) have been
  addressed in revision 11.
 
Protocol Quality
 
  The MIB module has been reviewed by Randy Presuhn. The overall quality
  with respect to DOCSIS functionality has been reviewed by Greg White
  and Eduardo Cardona. This document has been reviewed for the IESG by
  Bert Wijnen.

Note to RFC Editor
 
- Pls change first para of abstract (The table of contents has a ptr to
  sect 5.1, so that cover the changes from 2669).

  OLD:
  This memo is a revision of the standards track RFC 2669.  Please see
  "Revision Descriptions" below for a description of changes.  This
  document obsoletes RFC 2669.

  NEW:
  This memo is a revision of the standards track RFC 2669 and so it
  obsoletes RFC 2669.
  
- In the abstract, pls also expand the acronym DOCSIS and IPCDN

  DOCSIS - Data Over Cable Interface Specification.
  IPCDN  - IP over Cable Data Network.


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Tue Mar 28 16:52:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FOM7C-0005Dt-DS; Tue, 28 Mar 2006 16:52:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FOM7B-0005Dn-8A
	for ipcdn@ietf.org; Tue, 28 Mar 2006 16:52:37 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOM7A-0000Nm-Od
	for ipcdn@ietf.org; Tue, 28 Mar 2006 16:52:37 -0500
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k2SM8cZ4025308
	for <ipcdn@ietf.org>; Tue, 28 Mar 2006 15:08:38 -0700 (MST)
Received: from il06exm63.ds.mot.com (il06exm63.corp.mot.com [10.0.111.45])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id k2SM5dHs017804
	for <ipcdn@ietf.org>; Tue, 28 Mar 2006 16:05:39 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Mar 2006 15:52:34 -0600
Message-ID: <C48BF4C9FEC17F4AB373CFE3959BC1EC54552E@il06exm63.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SigMIB Draft 10
Thread-Index: AcZSsevmJnU4f9E+RmKKWfJgD6NSeA==
From: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>
To: <ipcdn@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08868c2bcdb53bddcb7cc7e7cf96b038
Subject: [ipcdn] SigMIB Draft 10
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2002950829=="
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2002950829==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C652B1.EC5D82DD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C652B1.EC5D82DD
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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_01C652B1.EC5D82DD
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<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 to=20
300 ms in duration.</FONT></P>
<P><FONT face=3DArial size=3D2>In the Belgium Belgacom document the =
RP-AS is implied=20
as being 340 ms and in field experience this as been verified. Some CPE =
devices=20
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 ring=20
cadence is acceptable.</FONT></P>
<P><FONT face=3DArial size=3D2>We therefore have two standards which do =
not overlap=20
and therefore we must define a new SigMIB object to define the RP-AS =
duration=20
from the ETSI 200 ms min to something in excess of the Belgacom nominal =
value of=20
340 ms.</FONT></P>
<P><FONT face=3DArial size=3D2>In the&nbsp;<SPAN =
class=3D298504221-28032006>following=20
text</SPAN>&nbsp;draft, I have defined a new object (#41) with a range =
of=20
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">&nbsp;&nbsp;=20
</SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object sets =
the duration=20
of <SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN><?xml:namespace prefix =
=3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" =
/><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">&nbsp;&nbsp; </SPAN>the =
ring pulse=20
alerting signal prior to CID signaling.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>Variations in <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">&nbsp;&nbsp; =
</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">&nbsp;&nbsp;=20
</SPAN>requirements.</FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
face=3DArial></FONT></FONT>&nbsp;</P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT><FONT =
face=3DArial=20
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>&nbsp;</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">&nbsp;&nbsp;=20
</SPAN>pktcSigDevrpAsDtsDuration<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </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 style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>SYNTAX<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>Unsigned32=20
(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 style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>UNITS<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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 style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>read-write=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>STATUS<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>current=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>following table defines the default values for this object<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>pktcSigDevCidMode<SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>Default <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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>duringringingETS<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>dtAsETS<SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>rpAsETS<SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>lrAsETS<SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
</SPAN>lrETS<SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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 style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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 style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>DEFVAL {&nbsp;<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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>::=3D =
{pktcSigDevConfigObjects=20
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 size=3D2>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>pktcInternationalGroup<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>OBJECT-GROUP<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECTS=20
{<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcNcsEndPntConfigPulseDialMaxBreakTime, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: yes">&nbsp;=20
</SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: yes">&nbsp; =

</SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevCidDelayAfterLR, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevCidDtmfStartCode, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevCidDtmfEndCode, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevVmwiSigProtocol, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevVmwiDelayAfterLR, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevVmwiDtmfStartCode, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevVmwiDtmfEndCode, <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P>
<P><FONT face=3DArial size=3D2>I understand it&nbsp;<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 Technical=20
Staff</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Science Advisory Board=20
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 =

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>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C652B1.EC5D82DD--


--===============2002950829==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--===============2002950829==--




From ipcdn-bounces@ietf.org Wed Mar 29 15:02:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FOgrq-0007by-Vw; Wed, 29 Mar 2006 15:02:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FOgrq-0007bZ-5t
	for ipcdn@ietf.org; Wed, 29 Mar 2006 15:02:10 -0500
Received: from pop-savannah.atl.sa.earthlink.net ([207.69.195.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOgrp-0006B7-Sc
	for ipcdn@ietf.org; Wed, 29 Mar 2006 15:02:10 -0500
Received: from h-68-166-188-37.snvacaid.dynamic.covad.net ([68.166.188.37]
	helo=oemcomputer)
	by pop-savannah.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FOgrc-0001He-00
	for ipcdn@ietf.org; Wed, 29 Mar 2006 15:01:56 -0500
Message-ID: <010801c6536c$122dc280$6401a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ipcdn@ietf.org>
References: <C48BF4C9FEC17F4AB373CFE3959BC1EC54552E@il06exm63.ds.mot.com>
Subject: Re: [ipcdn] SigMIB Draft 10
Date: Wed, 29 Mar 2006 12:05:01 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Hi -

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?

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.

Randy

----- Original Message ----- 
From: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>
To: <ipcdn@ietf.org>
Sent: Tuesday, March 28, 2006 1:52 PM
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  

   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.

 

Page 44 Add:

 

   pktcSigDevrpAsDtsDuration     OBJECT-TYPE 

       SYNTAX       Unsigned32 (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 rpAsETS. The  

             following table defines the default values for this object


             depending on the signal type: 

             pktcSigDevCidMode     Default 

             duringringingETS      not used 

             dtAsETS               not used 

             rpAsETS               250 

             lrAsETS               not used 

             lrETS                 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 } 

Page 60 Add last line

   pktcInternationalGroup    OBJECT-GROUP  

       OBJECTS {  

       pktcNcsEndPntConfigMinHookFlash,  

       pktcNcsEndPntConfigMaxHookFlash,  

       pktcNcsEndPntConfigPulseDialInterdigitTime,  

       pktcNcsEndPntConfigPulseDialMinMakeTime,  

       pktcNcsEndPntConfigPulseDialMaxMakeTime,  

       pktcNcsEndPntConfigPulseDialMinBreakTime,  

       pktcNcsEndPntConfigPulseDialMaxBreakTime, 

       pktcSigDevRingCadence,  

       pktcSigDevCidSigProtocol,  

       pktcSigDevCidDelayAfterLR, 

       pktcSigDevCidDtmfStartCode, 

       pktcSigDevCidDtmfEndCode, 

       pktcSigDevVmwiSigProtocol, 

       pktcSigDevVmwiDelayAfterLR, 

       pktcSigDevVmwiDtmfStartCode, 

       pktcSigDevVmwiDtmfEndCode, 

       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
 
 



--------------------------------------------------------------------------------


> _______________________________________________
> IPCDN mailing list
> IPCDN@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipcdn
> 


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Wed Mar 29 17:16:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FOiy3-0003Az-6K; Wed, 29 Mar 2006 17:16:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FOiy2-0003Au-0o
	for ipcdn@ietf.org; Wed, 29 Mar 2006 17:16:42 -0500
Received: from mms3.broadcom.com ([216.31.210.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOiy1-0003LI-H1
	for ipcdn@ietf.org; Wed, 29 Mar 2006 17:16:42 -0500
Received: from 10.10.64.154 by MMS3.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.0)); Wed, 29 Mar 2006 14:16:34 -0800
X-Server-Uuid: B238DE4C-2139-4D32-96A8-DD564EF2313E
Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id
	D90E82B0; Wed, 29 Mar 2006 14:16:33 -0800 (PST)
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id B48C92AF; Wed, 29 Mar
	2006 14:16:33 -0800 (PST)
Received: from mail-sj1-12.sj.broadcom.com (mail-sj1-12.sj.broadcom.com
	[10.16.128.215]) by mail-irva-8.broadcom.com (MOS 3.7.3a-GA) with ESMTP
	id DER51999; Wed, 29 Mar 2006 14:16:26 -0800 (PST)
Received: from NT-SJCA-0751.brcm.ad.broadcom.com (nt-sjca-0751
	[10.16.192.221]) by mail-sj1-12.sj.broadcom.com (Postfix) with ESMTP id
	A7A1220501; Wed, 29 Mar 2006 14:16:26 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] Feedback: draft-ietf-ipcdn-pktc-eventmess-05.txt
Date: Wed, 29 Mar 2006 14:16:24 -0800
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F48564AA7715@NT-SJCA-0751.brcm.ad.broadcom.com>
Thread-Topic: [ipcdn] Feedback: draft-ietf-ipcdn-pktc-eventmess-05.txt
Thread-Index: AcWh/HKIom44+HHgQGa23DAUEop9nw+NasHQE4lZg/AJR0M8sA==
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: ipcdn@ietf.org
X-TMWD-Spam-Summary: SEV=1.1; DFV=A2006032908; IFV=2.0.6,4.0-7; RPD=4.00.0004;
	RPDID=303030312E30413039303230322E34343242303637412E303033372D452D5046786C33494E497A33445631553653544639524F673D3D;
	ENG=IBF; TS=20060329221634; CAT=NONE; CON=NONE;
X-MMS-Spam-Filter-ID: A2006032908_4.00.0004_2.0.6,4.0-7
X-WSS-ID: 6835D8C83NG3979424-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Cc: Wim De Ketelaere <deketelaere@tcomlabs.com>
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

All,

After reviewing the draft-05, authors propose the following modifcations
to the draft-05:

1. Add the following normative references (Section 7):=20
	- PacketCable(TM) Management Event Mechanism Specification
(PKT-SP-MEM1.5-I01-050128) - to be reffered to by the section 3 and some
MIB Objects
	- J. Postel, "User Datagram Protocol", STD0006, RFC 768 - to be
refered to by section 3.6.
	- C. Lonvick, "The BSD syslog Protocol", RFC 3164, August 2001 -
to be reffered to by some MIB Objects.

2. Rename the following MIB Objects to stay consistant in terminology
with RFC3164 ("BSD Syslog protocol"):
	- pktcDevEvReportingLevel        to pktcDevEvSeverityLevel
	- pktcDevEventClassReportLevel   to
pktcDevEventClassSeverityLevel
	- pktcDevEventDescrLevel         to
pktcDevEventDescrSeverityLevel

3. The following references are updated in Sections 7 and 8:
[PKT-SP-PROV], [PKT-SP-MGCP], [PKT-SP-CODEC] according to the new
versions of the PacketCable Specifications issued.

4. The Following Textual Conventions are introduced:

4.1. EventClass - to simplify the syntax for pktcDevEventClass, and
pktcDevEventDescrClass MIB Objects

EventClass ::=3D TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "This textual convention represents the identifier=20
        of the Event class supported by the MTA. The Event=20
        Class is used to allow the MTA to group together=20
        various events related to each other."
    SYNTAX   SnmpAdminString (SIZE (1..????)

Co-authors did not have the consensus on whether the SnmpAdminString
should or should not have the max size restriction. Authors are
requesting folks on this mailing list to provide the feedback on this
issue.

4.2. SeverityLevel - to simplify the syntax for pktcDevEvSeverityLevel,
pktcDevEventClassSeverityLevel, and pktcDevEventDescrSeverityLevel MIB
Objects.

SeverityLevel ::=3D TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
        "This textual convention represents the severity
        levels for the various events reported by the MTA.
        The levels are as described below:
            emergency(0) - A condition that makes the system=20
                           unusable.
            alert(1)     - A service-affecting condition for which
                           immediate action must be taken.
            critical(2)  - A service-affecting critical condition.
            error(3)     - An error condition.
            warning(4)   - A warning condition.
            notice(5)    - A normal but significant condition.
            info(6)      - An informational message.
            debug(7)     - A debug message."
    SYNTAX      BITS {
                emergency(0),
                alert(1),
                critical(2), =20
                error(3), =20
                warning(4), =20
                notice(5),
                info(6),
                debug(7)=20
                }

5. The following MIB Objects have been modified:

5.1. pktcDevEvControl: DECSRIPTION clause has been modified to clarify
the behavior of the MTA when resetEventLogTable(0) bit is set. Affected
part is:

            "Setting the resetEventLogTable(0) bit to
            a value of '1' clears the entire event log:=20
               - deletes all entries in pktcDevEventLogTable,
               - resets the value of pktcDevEvLogIndex to '0'.
            MTA MUST perform the same actions regardless of=20
            whether the pktcDevEventLogTable is persistent in=20
            non-volatile memory or not.:

5.2. pktcDevEvSyslogAddressType - added the following:
    REFERENCE
            "PacketCable MTA Device Provisioning Specification,=20
            [PKT-SP-PROV]."
    DEFVAL { ipv4 }

5.3. pktcDevEvSyslogAddress  - added the following:
    REFERENCE
            "PacketCable MTA Device Provisioning Specification,=20
            [PKT-SP-PROV];
            PacketCable Management Event Mechanism Specification,
            [PKT-SP-MEM1.5];
            RFC 3164, The BSD syslog Protocol, [RFC3164]."

5.4. pktcDevEvSyslogUdpPort  - added the following:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."

5.5. pktcDevEvSeverityLevel:
	- SYNTAX changed to SeverityLevel
	- added the following:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."

5.6. pktcDevEventClassReportEntry - DECSRIPTION modified to be the
following:
    DESCRIPTION
            "For each event class defined by a vendor for=20
            the events described in the 'pktcDevEventDescrTable',
            MTA MUST create a corresponding entry in this table.

            If an MTA does not define event classes,
            then MTA MUST create one entry for  the event=20
            class 'generic'."

5.7. PktcDevEventClassReportEntry - modified to use new SYNTAX for two
obejcts: pktcDevEventClass and pktcDevEventClassSeverityLevel:
	PktcDevEventClassReportEntry::=3D SEQUENCE {
    pktcDevEventClass                EventClass,
    pktcDevEventReportStatus         TruthValue,
    pktcDevEventClassSeverityLevel   SeverityLevel
    } =20

5.8. pktcDevEventClass:
	- SYNTAX changed to EventClass
	- DESCRCIPTOIN clause modified to be the following:

    DESCRIPTION
        "This MIB Object contains the identifier=20
         of an event class supported by the device.
         Vendors MAY define different event classes=20
         (e.g. DHCP, SNMP, DEBUG) to group together=20
         related events. It is expected that vendors=20
         use well-chosen names for the classes.=20
         If an MTA does not define event classes,
         then the value of this MIB Object MUST be set=20
         to 'generic'."

5.9. pktcDevEventClassSeverityLevel: added REFERENCE clause:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."

5.10. PktcDevEventDescrEntry	- modified to use new SYNTAX for two
obejcts: pktcDevEventDescrSeverityLevel and pktcDevEventDescrClass:
	PktcDevEventDescrEntry::=3D SEQUENCE {
	    pktcDevEventDescrId              Unsigned32,
	    pktcDevEventDescrEnterprise      Unsigned32,
	    pktcDevEventDescrFacility        INTEGER,
	    pktcDevEventDescrSeverityLevel   SeverityLevel,
	    pktcDevEventDescrReporting       BITS,
	    pktcDevEventDescrText            SnmpAdminString,
	    pktcDevEventDescrClass           EventClass
	    } =20

5.11. pktcDevEventDescrId - REFERENCE clause added:
    REFERENCE
            "PacketCable Management Event Mechanism Specification,
            [PKT-SP-MEM1.5];
            PacketCable MTA Device Provisioning Specification,=20
            [PKT-SP-PROV]."

5.12. pktcDevEventDescrFacility - REFERENCE clause added:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."


5.13. pktcDevEventDescrSeverityLevel:
	- SYNTAX changed to SeverityLevel
	- REFERNCE clause added:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."


5.14. pktcDevEventDescrClass:
	- SYNTAX changed to EventClass
	- MAX-ACCESS changed to "read-only" to avoid cross-reference
consistency complications with pktcDevEventClassReportTable.

5.15. pktcDevEventLogTable - the following added to the end of the
DESCRIPTION clause:
	"The content of the table may or may not persist in the
non-volatile memory."

5.16. pktcDevEvLogTime:
	- the following clarification is made in the DESCRIPTION clause
(as per RFC3164):
	      "This MIB Object provides a human-readable description=20
            of the local time at which the event occurred."
                   ^^^^^
	- REFERENCE clause is added:
    REFERENCE
            "RFC 3164, The BSD syslog Protocol, [RFC3164]."

5.17. pktcDevEvLogCorrelationId:=20
	- the following has been added to the end of the DECRIPTION
clause:
            "Though Correlation-ID, once generated after MTA
            reset, does not change until next MTA reset, the=20
            value of this object will differ for the events=20
            preserved across MTA resets in case of the persistent=20
            pktcDevEventLogTable."
	- REFERENCE clause added:
    REFERENCE
            "PacketCable MTA Device Provisioning Specification,=20
            [PKT-SP-PROV]."

5.18. pktcDevEvLogAdditionalInfo - the following clarification has been
made to the DESCRIPTION clause:
	- old text:
		"However, the MTA is nto required to implement this
funcitoinlaity.",=20
	- new text:
            "If MTA does not provide any additional=20
            information for the particular even generated, it MUST=20
            leave this object empty and return zero-length string."
=20

Eugene.

-----Original Message-----
From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf
Of Sumanth Channabasappa
Sent: Friday, February 10, 2006 7:39 AM
To: ipcdn@ietf.org
Subject: [ipcdn] Feedback: draft-ietf-ipcdn-pktc-eventmess-05.txt

Folks,

I have not received any comments on the "PacketCable/IPCablecom
Management Event MIB" draft-05
(ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-05.t
xt)

I would request folks on this mailing list to review and bring to my
attention any questions, comments or suggestions (apologies if I missed
any comments, don't recall any on this mailing list).

The last email on this topic was a summary of changes from draft-04 and
can be found at:

http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01810.html (Nov
2, 2005)


Thanks!
Sumanth



_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



From ipcdn-bounces@ietf.org Thu Mar 30 12:00:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FP0W0-0003bP-Ke; Thu, 30 Mar 2006 12:00:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FP0Vz-0003Ya-LC
	for ipcdn@ietf.org; Thu, 30 Mar 2006 12:00:55 -0500
Received: from pacdcoavas09.cable.comcast.com ([208.17.33.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FP0Vz-000601-2w
	for ipcdn@ietf.org; Thu, 30 Mar 2006 12:00:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] SigMIB Draft 10
Date: Thu, 30 Mar 2006 12:00:29 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF9A0@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ipcdn] SigMIB Draft 10
Thread-Index: AcZSsevmJnU4f9E+RmKKWfJgD6NSeABZmPLw
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>,
	<ipcdn@ietf.org>
X-OriginalArrivalTime: 30 Mar 2006 17:00:30.0609 (UTC)
	FILETIME=[738CB810:01C6541B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39821207e2a2cade5c69c89d23fb80ee
Cc: 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1294324558=="
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1294324558==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6541B.72BF8544"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6541B.72BF8544
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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:phillipfreyman@motorola.com]=20
Sent: Tuesday, March 28, 2006 4:53 PM
To: ipcdn@ietf.org
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_01C6541B.72BF8544
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=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2>Phillip,</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>Pardon=20
my ignorance with this question. What is the difference between the =
proposed=20
object below ('pktcSigDevrpAsDtsDuration') and the =
'pktcSigDevCidAfterRPAS' in=20
the current -10 draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>I am=20
not&nbsp;so much&nbsp;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 =

size=3D2></FONT></SPAN>&nbsp;</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=20
and get it published.</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =
Tuesday,=20
  March 28, 2006 4:53 PM<BR><B>To:</B> ipcdn@ietf.org<BR><B>Subject:</B> =
[ipcdn]=20
  SigMIB Draft 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 to=20
  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&nbsp;<SPAN=20
  class=3D298504221-28032006>following text</SPAN>&nbsp;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 =

  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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the duration=20
  of <SPAN style=3D"mso-spacerun: =
yes">&nbsp;</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">&nbsp;&nbsp; </SPAN>the =
ring pulse=20
  alerting signal prior to CID signaling.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>Variations in <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">&nbsp;&nbsp; =
</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">&nbsp;&nbsp;=20
  </SPAN>requirements.</FONT></FONT></P>
  <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial></FONT></FONT>&nbsp;</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>&nbsp;</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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>SYNTAX<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>UNITS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>STATUS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>current=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>following table defines the default values for this object<SPAN =

  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>pktcSigDevCidMode<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>duringringingETS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>dtAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>rpAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>lrAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>lrETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>DEFVAL=20
  {&nbsp;<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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;</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 size=3D2>
  <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20
  face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
  </SPAN>pktcInternationalGroup<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECT-GROUP<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECTS=20
  {<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P>
  <P><FONT face=3DArial size=3D2>I understand it&nbsp;<SPAN=20
  class=3D298504221-28032006>may delay </SPAN>Draft 10 but I think it is =

  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 Technical=20
  Staff</FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>Science Advisory Board=20
  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 =

  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>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C6541B.72BF8544--


--===============1294324558==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--===============1294324558==--




From ipcdn-bounces@ietf.org Thu Mar 30 12:16:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FP0lS-0001lo-Vb; Thu, 30 Mar 2006 12:16:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FP0lR-0001le-Hl
	for ipcdn@ietf.org; Thu, 30 Mar 2006 12:16:53 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FP0lQ-0006jp-TD
	for ipcdn@ietf.org; Thu, 30 Mar 2006 12:16:53 -0500
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k2UHWvU7013730
	for <ipcdn@ietf.org>; Thu, 30 Mar 2006 10:32:57 -0700 (MST)
Received: from il06exm63.ds.mot.com (il06exm63.corp.mot.com [10.0.111.45])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k2UHUcib013961
	for <ipcdn@ietf.org>; Thu, 30 Mar 2006 11:30:38 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] SigMIB Draft 10
Date: Thu, 30 Mar 2006 11:16:50 -0600
Message-ID: <C48BF4C9FEC17F4AB373CFE3959BC1EC582D95@il06exm63.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ipcdn] SigMIB Draft 10
Thread-Index: AcZSsevmJnU4f9E+RmKKWfJgD6NSeABZmPLwAAEU+EA=
From: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, <ipcdn@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 285c5d2442d4c903d8dda55de04f5334
Cc: 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2115304448=="
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2115304448==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6541D.BC8DFDC8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6541D.BC8DFDC8
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

________________________________

From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]=20
Sent: Thursday, March 30, 2006 11:00 AM
To: Freyman Phillip-FPF300; ipcdn@ietf.org
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:phillipfreyman@motorola.com]=20
	Sent: Tuesday, March 28, 2006 4:53 PM
	To: ipcdn@ietf.org
	Subject: [ipcdn] SigMIB Draft 10
=09
=09

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

	   national standards cause CID failure if RP-AS is not defined
by local=20

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

	             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_01C6541D.BC8DFDC8
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><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;&nbsp;=20
</SPAN>pktcSigDevCidAfterRPAS - this international object sets the =
<STRONG><FONT=20
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">&nbsp;&nbsp;=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">&nbsp;&nbsp;=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=20
size=3D2>&nbsp;&nbsp;&nbsp; =
</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&nbsp;as</FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT =
size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT><FONT size=3D2><SPAN class=3D645000917-30032006>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>pktcSigDevrpAsDtsDuration &#8211; this=20
international object sets the <FONT color=3D#ff0000=20
size=3D3><STRONG>duration</STRONG></FONT> of <SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>the ring pulse alerting =
signal=20
prior to CID signaling.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>Variations=20
in <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>national standards cause =
CID=20
failure if RP-AS is not defined by local <o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>requirements.<o:p></o:p></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</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>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D645000917-30032006>C<SPAN =
class=3D645000917-30032006>idAfterRPAS&nbsp;is the=20
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>&nbsp;</DIV=
>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D645000917-30032006><SPAN class=3D645000917-30032006>Hopefully =
this explains=20
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>&nbsp;</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>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D645000917-30032006></SPAN></FONT></FONT></FONT>&nbsp;</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:Richard_Woundy@cable.comcast.com] <BR><B>Sent:</B> Thursday, =
March 30,=20
2006 11:00 AM<BR><B>To:</B> Freyman Phillip-FPF300;=20
ipcdn@ietf.org<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 =

size=3D2>Phillip,</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>Pardon=20
my ignorance with this question. What is the difference between the =
proposed=20
object below ('pktcSigDevrpAsDtsDuration') and the =
'pktcSigDevCidAfterRPAS' in=20
the current -10 draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>I am=20
not&nbsp;so much&nbsp;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 =

size=3D2></FONT></SPAN>&nbsp;</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=20
and get it published.</FONT></SPAN></DIV>
<DIV><SPAN class=3D970013816-30032006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =
Tuesday,=20
  March 28, 2006 4:53 PM<BR><B>To:</B> ipcdn@ietf.org<BR><B>Subject:</B> =
[ipcdn]=20
  SigMIB Draft 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 to=20
  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&nbsp;<SPAN=20
  class=3D298504221-28032006>following text</SPAN>&nbsp;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 =

  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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the duration=20
  of <SPAN style=3D"mso-spacerun: =
yes">&nbsp;</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">&nbsp;&nbsp; </SPAN>the =
ring pulse=20
  alerting signal prior to CID signaling.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>Variations in <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">&nbsp;&nbsp; =
</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">&nbsp;&nbsp;=20
  </SPAN>requirements.</FONT></FONT></P>
  <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial></FONT></FONT>&nbsp;</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>&nbsp;</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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>SYNTAX<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>UNITS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>STATUS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>current=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>following table defines the default values for this object<SPAN =

  style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>pktcSigDevCidMode<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>duringringingETS<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>dtAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>rpAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>lrAsETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  </SPAN>lrETS<SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>DEFVAL=20
  {&nbsp;<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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;</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 size=3D2>
  <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT=20
  face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
  </SPAN>pktcInternationalGroup<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECT-GROUP<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECTS=20
  {<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P>
  <P><FONT face=3DArial size=3D2>I understand it&nbsp;<SPAN=20
  class=3D298504221-28032006>may delay </SPAN>Draft 10 but I think it is =

  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 Technical=20
  Staff</FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>Science Advisory Board=20
  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 =

  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>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C6541D.BC8DFDC8--


--===============2115304448==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--===============2115304448==--




From ipcdn-bounces@ietf.org Thu Mar 30 17:34:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FP5iL-00077x-NV; Thu, 30 Mar 2006 17:34:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FP5iK-00077s-1Q
	for ipcdn@ietf.org; Thu, 30 Mar 2006 17:34:00 -0500
Received: from paoakoavas09.cable.comcast.com ([208.17.35.58]
	helo=cable.comcast.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FP5iJ-0003im-8r
	for ipcdn@ietf.org; Thu, 30 Mar 2006 17:34:00 -0500
Received: from ([10.20.9.172])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-TDCH7.18214553;
	Thu, 30 Mar 2006 17:33:37 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 30 Mar 2006 17:33:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] SigMIB Draft 10
Date: Thu, 30 Mar 2006 17:32:22 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF9BC@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ipcdn] SigMIB Draft 10
Thread-Index: AcZSsevmJnU4f9E+RmKKWfJgD6NSeABZmPLwAAEU+EAACtWZ4A==
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>,
	<ipcdn@ietf.org>
X-OriginalArrivalTime: 30 Mar 2006 22:33:25.0903 (UTC)
	FILETIME=[F5C0B1F0:01C65449]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d3dffd2aefc0f55425d5c0046903fc08
Cc: 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1287609269=="
Errors-To: ipcdn-bounces@ietf.org

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:phillipfreyman@motorola.com]=20
Sent: Thursday, March 30, 2006 12:17 PM
To: Woundy, Richard; ipcdn@ietf.org
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:Richard_Woundy@cable.comcast.com]=20
Sent: Thursday, March 30, 2006 11:00 AM
To: Freyman Phillip-FPF300; ipcdn@ietf.org
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:phillipfreyman@motorola.com]=20
Sent: Tuesday, March 28, 2006 4:53 PM
To: ipcdn@ietf.org
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>&nbsp;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006><FONT size=3D2><FONT face=3DArial=20
color=3D#0000ff>&gt;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006>Maybe what is implied is "The =
value of this=20
object is&nbsp;ignored<FONT size=3D2><FONT face=3DArial>&nbsp;unless=20
pktcSigDevCidMode is rpAsETS.</FONT></FONT>"? I agree that the wording =
could be=20
clearer.</SPAN></DIV>
<DIV><SPAN =
class=3D969131922-30032006></SPAN>&nbsp;</DIV></FONT></SPAN><SPAN=20
class=3D969131922-30032006><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D969131922-30032006>&gt;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
tend&nbsp;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&nbsp;could be set to&nbsp;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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =
Thursday,=20
  March 30, 2006 12:17 PM<BR><B>To:</B> Woundy, Richard;=20
  ipcdn@ietf.org<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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;&nbsp;=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">&nbsp;&nbsp;=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">&nbsp;&nbsp;=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>&nbsp;&nbsp;&nbsp; =
</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&nbsp;as</FONT></DIV>
  <DIV><FONT face=3D"Courier New"><FONT =
size=3D2></FONT></FONT>&nbsp;</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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the <FONT=20
  color=3D#ff0000 size=3D3><STRONG>duration</STRONG></FONT> of <SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</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">&nbsp;&nbsp; =
</SPAN>the=20
  ring pulse alerting signal prior to CID signaling.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;=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">&nbsp;&nbsp;=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">&nbsp;</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>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
  class=3D645000917-30032006>C<SPAN =
class=3D645000917-30032006>idAfterRPAS&nbsp;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>&nbsp;</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>&nbsp;</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>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
  class=3D645000917-30032006></SPAN></FONT></FONT></FONT>&nbsp;</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:Richard_Woundy@cable.comcast.com] <BR><B>Sent:</B> Thursday, =
March 30,=20
  2006 11:00 AM<BR><B>To:</B> Freyman Phillip-FPF300;=20
  ipcdn@ietf.org<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>&nbsp;</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>&nbsp;</DIV>
  <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial =
color=3D#0000ff size=3D2>I am=20
  not&nbsp;so much&nbsp;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>&nbsp;</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>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =

    Tuesday, March 28, 2006 4:53 PM<BR><B>To:</B>=20
    ipcdn@ietf.org<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&nbsp;<SPAN=20
    class=3D298504221-28032006>following text</SPAN>&nbsp;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">&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the=20
    duration of <SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;</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">&nbsp;&nbsp; =
</SPAN>the ring=20
    pulse alerting signal prior to CID signaling.<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp; =
</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">&nbsp;&nbsp;=20
    </SPAN>requirements.</FONT></FONT></P>
    <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
    face=3DArial></FONT></FONT>&nbsp;</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>&nbsp;</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">&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>SYNTAX<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>UNITS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>STATUS<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>following table defines the default values for this =
object<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>pktcSigDevCidMode<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>duringringingETS<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>dtAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>rpAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>lrAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>lrETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>DEFVAL=20
    {&nbsp;<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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;</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">&nbsp;&nbsp;=20
    </SPAN>pktcInternationalGroup<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECT-GROUP<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>OBJECTS {<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P>
    <P><FONT face=3DArial size=3D2>I understand it&nbsp;<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>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
    color=3D#0000ff =
size=3D2></FONT>&nbsp;</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
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--===============1287609269==--




From ipcdn-bounces@ietf.org Fri Mar 31 00:08:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FPBrv-0005PR-DJ; Fri, 31 Mar 2006 00:08:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FPBru-0005MA-CN
	for ipcdn@ietf.org; Fri, 31 Mar 2006 00:08:18 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPBrt-0004PS-Gd
	for ipcdn@ietf.org; Fri, 31 Mar 2006 00:08:18 -0500
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k2V5OMi1021785
	for <ipcdn@ietf.org>; Thu, 30 Mar 2006 22:24:22 -0700 (MST)
Received: from il06exm63.ds.mot.com (il06exm63.corp.mot.com [10.0.111.45])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k2V5M3tr019595
	for <ipcdn@ietf.org>; Thu, 30 Mar 2006 23:22:04 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] SigMIB Draft 10
Date: Thu, 30 Mar 2006 23:08:15 -0600
Message-ID: <C48BF4C9FEC17F4AB373CFE3959BC1EC582F29@il06exm63.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ipcdn] SigMIB Draft 10
Thread-Index: AcZSsevmJnU4f9E+RmKKWfJgD6NSeABZmPLwAAEU+EAACtWZ4AAOEEVg
From: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, <ipcdn@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d7802e9da0b1d11bf32ba03c41071b61
Cc: 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2084718056=="
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2084718056==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C65481.1E872D3D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C65481.1E872D3D
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Richard, Randy,
=20
per Randy's comment on text. =20
=20
In my proposal, I picked up the format and text from other elements in
the current proposed SigMIB Draft 10.  This text has been in WG
discussion for a long time.
=20
I contacted Gordon Beacham of Motorola who was an earlier member of the
WG on this question.
=20
although Gordon did not have specific email chain on the discussion in
this area, he remembers that this was the wording recommended by the
working group and was answered long ago on the ipcdn reflector.=20
=20
As Gordon recalled, "not used" meant the value is not applicable to a
particular object. Somebody wanted to know what happens if a get/set was
used, so the suggestion was to return inconsistent value.=20
=20
If you have an opinion for different wording that is clearer please post
it for discussion.
=20
regards,
=20
Phil
=20
=20

________________________________

From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]=20
Sent: Thursday, March 30, 2006 4:32 PM
To: Freyman Phillip-FPF300; ipcdn@ietf.org
Subject: RE: [ipcdn] SigMIB Draft 10


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:phillipfreyman@motorola.com]=20
	Sent: Thursday, March 30, 2006 12:17 PM
	To: Woundy, Richard; ipcdn@ietf.org
	Subject: RE: [ipcdn] SigMIB Draft 10
=09
=09
	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=20

	   national standards cause CID failure if RP-AS is not defined
by local=20

	   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

________________________________

	From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]=20
	Sent: Thursday, March 30, 2006 11:00 AM
	To: Freyman Phillip-FPF300; ipcdn@ietf.org
	Subject: RE: [ipcdn] SigMIB Draft 10
=09
=09
	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:phillipfreyman@motorola.com]=20
		Sent: Tuesday, March 28, 2006 4:53 PM
		To: ipcdn@ietf.org
		Subject: [ipcdn] SigMIB Draft 10
	=09
	=09

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

		   national standards cause CID failure if RP-AS is not
defined by local=20

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

		             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


		            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_01C65481.1E872D3D
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><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Richard, Randy,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>per Randy's comment on text.&nbsp; =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In my proposal, I picked up the format and text =
from other=20
elements in the current proposed SigMIB Draft 10.&nbsp; This text has =
been in WG=20
discussion for a long time.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I contacted Gordon Beacham of Motorola who was =
an earlier=20
member of the WG on this question.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>although Gordon did not have specific =
email chain on=20
the discussion in this area, he remembers that<SPAN=20
class=3D820365922-30032006>&nbsp;this was the wording recommended by the =
working=20
group and was answered long ago on the ipcdn=20
reflector.</SPAN></FONT></FONT></FONT>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D820365922-30032006></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>As&nbsp;<SPAN =
class=3D947540105-31032006>Gordon</SPAN>=20
recall<SPAN class=3D947540105-31032006>ed</SPAN>,&nbsp;<SPAN=20
class=3D947540105-31032006>"</SPAN>not used<SPAN =
class=3D947540105-31032006>"</SPAN>=20
meant the value is not applicable to a particular object. Somebody =
wanted to=20
know what happens if a get/set&nbsp;was used, =
so&nbsp;the&nbsp;suggestion was to=20
return inconsistent value.&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If&nbsp;<SPAN class=3D947540105-31032006>you=20
have</SPAN>&nbsp;an opinion for different wording that is =
clearer&nbsp;<SPAN=20
class=3D947540105-31032006>please post it for=20
discussion</SPAN>.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><SPAN=20
class=3D947540105-31032006><FONT face=3DArial color=3D#0000ff=20
size=3D2>regards,</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><SPAN=20
class=3D947540105-31032006><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D820365922-30032006><SPAN=20
class=3D947540105-31032006><FONT face=3DArial color=3D#0000ff=20
size=3D2>Phil</FONT></SPAN></SPAN></DIV></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D947540105-31032006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<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:Richard_Woundy@cable.comcast.com] <BR><B>Sent:</B> Thursday, =
March 30,=20
2006 4:32 PM<BR><B>To:</B> Freyman Phillip-FPF300;=20
ipcdn@ietf.org<BR><B>Subject:</B> RE: [ipcdn] SigMIB Draft=20
10<BR></FONT><BR></DIV>
<DIV></DIV>
<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>&nbsp;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006><FONT size=3D2><FONT face=3DArial=20
color=3D#0000ff>&gt;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006>Maybe what is implied is "The =
value of this=20
object is&nbsp;ignored<FONT size=3D2><FONT face=3DArial>&nbsp;unless=20
pktcSigDevCidMode is rpAsETS.</FONT></FONT>"? I agree that the wording =
could be=20
clearer.</SPAN></DIV>
<DIV><SPAN =
class=3D969131922-30032006></SPAN>&nbsp;</DIV></FONT></SPAN><SPAN=20
class=3D969131922-30032006><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D969131922-30032006>&gt;</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>&nbsp;</DIV>
<DIV><SPAN class=3D969131922-30032006><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
tend&nbsp;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&nbsp;could be set to&nbsp;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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =
Thursday,=20
  March 30, 2006 12:17 PM<BR><B>To:</B> Woundy, Richard;=20
  ipcdn@ietf.org<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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;&nbsp;=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">&nbsp;&nbsp;=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">&nbsp;&nbsp;=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>&nbsp;&nbsp;&nbsp; =
</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&nbsp;as</FONT></DIV>
  <DIV><FONT face=3D"Courier New"><FONT =
size=3D2></FONT></FONT>&nbsp;</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">&nbsp;&nbsp;=20
  </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the <FONT=20
  color=3D#ff0000 size=3D3><STRONG>duration</STRONG></FONT> of <SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</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">&nbsp;&nbsp; =
</SPAN>the=20
  ring pulse alerting signal prior to CID signaling.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;=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">&nbsp;&nbsp;=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">&nbsp;</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>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
  class=3D645000917-30032006>C<SPAN =
class=3D645000917-30032006>idAfterRPAS&nbsp;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>&nbsp;</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>&nbsp;</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>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
  class=3D645000917-30032006></SPAN></FONT></FONT></FONT>&nbsp;</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:Richard_Woundy@cable.comcast.com] <BR><B>Sent:</B> Thursday, =
March 30,=20
  2006 11:00 AM<BR><B>To:</B> Freyman Phillip-FPF300;=20
  ipcdn@ietf.org<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>&nbsp;</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>&nbsp;</DIV>
  <DIV><SPAN class=3D970013816-30032006><FONT face=3DArial =
color=3D#0000ff size=3D2>I am=20
  not&nbsp;so much&nbsp;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>&nbsp;</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>&nbsp;</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:phillipfreyman@motorola.com] <BR><B>Sent:</B> =

    Tuesday, March 28, 2006 4:53 PM<BR><B>To:</B>=20
    ipcdn@ietf.org<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&nbsp;<SPAN=20
    class=3D298504221-28032006>following text</SPAN>&nbsp;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">&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration &#8211; this international object =
sets the=20
    duration of <SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;</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">&nbsp;&nbsp; =
</SPAN>the ring=20
    pulse alerting signal prior to CID signaling.<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp; =
</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">&nbsp;&nbsp;=20
    </SPAN>requirements.</FONT></FONT></P>
    <P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
    face=3DArial></FONT></FONT>&nbsp;</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>&nbsp;</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">&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>SYNTAX<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>UNITS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>MAX-ACCESS<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>STATUS<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>FSK or DTMF containing the Caller ID information. It is<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>only used when pktcSigDevCidMode is rpAsETS. The<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>following table defines the default values for this =
object<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>pktcSigDevCidMode<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>duringringingETS<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>dtAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>rpAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>lrAsETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    </SPAN>lrETS<SPAN=20
    style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>REFERENCE<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>DEFVAL=20
    {&nbsp;<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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN><SPAN style=3D"mso-spacerun: yes">&nbsp;</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">&nbsp;&nbsp;=20
    </SPAN>pktcInternationalGroup<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; =
</SPAN>OBJECT-GROUP<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>OBJECTS {<SPAN style=3D"mso-spacerun: yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigMinHookFlash,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigMaxHookFlash,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialInterdigitTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMinMakeTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMaxMakeTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcNcsEndPntConfigPulseDialMinBreakTime,<SPAN=20
    style=3D"mso-spacerun: yes">&nbsp; </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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevRingCadence,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevCidSigProtocol,<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN>pktcSigDevrpAsDtsDuration,</FONT></FONT></SPAN></P>
    <P><FONT face=3DArial size=3D2>I understand it&nbsp;<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>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
    color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C65481.1E872D3D--


--===============2084718056==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

--===============2084718056==--




From ipcdn-bounces@ietf.org Fri Mar 31 01:00:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FPCfz-0005gA-VU; Fri, 31 Mar 2006 01:00:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FPCfy-0005g3-Uq
	for ipcdn@ietf.org; Fri, 31 Mar 2006 01:00:02 -0500
Received: from pop-savannah.atl.sa.earthlink.net ([207.69.195.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPCfx-0006Zz-O0
	for ipcdn@ietf.org; Fri, 31 Mar 2006 01:00:02 -0500
Received: from h-68-165-6-39.snvacaid.dynamic.covad.net ([68.165.6.39]
	helo=oemcomputer)
	by pop-savannah.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1FPCfs-0004N3-00
	for ipcdn@ietf.org; Fri, 31 Mar 2006 00:59:56 -0500
Message-ID: <001801c65488$c4dad900$6401a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ipcdn@ietf.org>
References: <C48BF4C9FEC17F4AB373CFE3959BC1EC582F29@il06exm63.ds.mot.com>
Subject: Re: [ipcdn] SigMIB Draft 10
Date: Thu, 30 Mar 2006 22:03:00 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>,
	<mailto:ipcdn-request@ietf.org?subject=subscribe>
Errors-To: ipcdn-bounces@ietf.org

Hi -

> From: "Freyman Phillip-FPF300" <phillipfreyman@motorola.com>
> To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>; <ipcdn@ietf.org>
> Sent: Thursday, March 30, 2006 9:08 PM
> Subject: RE: [ipcdn] SigMIB Draft 10
...
> As Gordon recalled, "not used" meant the value is not applicable to a
> particular object. Somebody wanted to know what happens if a get/set was
> used, so the suggestion was to return inconsistent value. 
...

Returning a "inconsistent value" in response to an SNMP get(next/bulk)
operation is simply wrong.  See RFC 3416 sections 4.2.1, 4.2.2,
and 4.2.3 respectively for the permitted responses.  So the question
still remains: how do these objects behave in the "not used" case?
The behaviour I'd expect would be for these objects to be present with
whatever value they had most recently been set to, which might be the
result of DEFVAL initialization.

In the case of a set request, "inconsistent value" would be a plausible
response, but it does mean that systems using SNMP to configure a
device will need to send the varbinds in separate PDUs to ensure consistent
results.  I don't see how this benefits anyone.

Randy


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



