From ipcdn-bounces@ietf.org Tue Oct 10 04:16:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GXCmL-000476-Ki; Tue, 10 Oct 2006 04:15:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GXCmK-00043k-Ls
	for ipcdn@ietf.org; Tue, 10 Oct 2006 04:15:56 -0400
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXCmJ-0002TJ-Dg
	for ipcdn@ietf.org; Tue, 10 Oct 2006 04:15:56 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k9A84Ohq014663
	for <ipcdn@ietf.org>; Tue, 10 Oct 2006 04:04:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 10 Oct 2006 10:15:49 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B54BAD6@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RETURNED MAIL: DATA FORMAT ERROR
Thread-Index: AcbsREtcs7dfwhRZQg61bM39YiOUUQAAAATG
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ipcdn@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [ipcdn] Out of Office AutoReply: RETURNED MAIL: DATA FORMAT ERROR
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="===============1078677506=="
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1078677506==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6EC44.4B6D8DE9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6EC44.4B6D8DE9
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am out of office on a business trip followed by vacation. I will be =
back on October 12, 2006.  I may not read and respond to e-mails during =
this period.  If you need to contact me urgently, please leave a voice =
mail message at my office number.

Regards,

Dan


------_=_NextPart_001_01C6EC44.4B6D8DE9
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6617.47">
<TITLE>Out of Office AutoReply: RETURNED MAIL: DATA FORMAT ERROR</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am out of office on a business trip followed by =
vacation. I will be back on October 12, 2006.&nbsp; I may not read and =
respond to e-mails during this period.&nbsp; If you need to contact me =
urgently, please leave a voice mail message at my office number.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6EC44.4B6D8DE9--


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

--===============1078677506==--




From ipcdn-bounces@ietf.org Thu Oct 12 11:39:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY2dT-0001DR-6z; Thu, 12 Oct 2006 11:38:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY2dS-0001DG-2E
	for ipcdn@ietf.org; Thu, 12 Oct 2006 11:38:14 -0400
Received: from soda.ext.ti.com ([198.47.26.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY2dM-0006fC-NB
	for ipcdn@ietf.org; Thu, 12 Oct 2006 11:38:14 -0400
Received: from dlep35.itg.ti.com ([157.170.170.118])
	by soda.ext.ti.com (8.13.7/8.13.7) with ESMTP id k9CFbM3i009726
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Oct 2006 10:37:32 -0500
Received: from dlep95.itg.ti.com (localhost [127.0.0.1])
	by dlep35.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9CFbG8m019579;
	Thu, 12 Oct 2006 10:37:16 -0500 (CDT)
Received: from dsbe71.ent.ti.com (localhost [127.0.0.1])
	by dlep95.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9CFbGH0028248;
	Thu, 12 Oct 2006 10:37:16 -0500 (CDT)
Received: from dlee05.ent.ti.com ([157.170.170.71]) by dsbe71.ent.ti.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Oct 2006 10:37:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Oct 2006 10:37:15 -0500
Message-ID: <27C82141AA835A428C2EF784424B0D1C054A9304@dlee05.ent.ti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: pktcSigDevToneDbLevel modifying default value and range-Sig mib
	draft-11
Thread-Index: AcbuFEtviMz1f0jJRdiqLtEPmiYrRw==
From: "Kumar, Satish" <satish.kumar@ti.com>
To: "Ipcdn \(E-mail\)" <ipcdn@ietf.org>
X-OriginalArrivalTime: 12 Oct 2006 15:37:16.0807 (UTC)
	FILETIME=[4BFA0170:01C6EE14]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Sanchez, Mauricio" <msanchez@ti.com>,
	Freyman Phillip-FPF300 <phillipfreyman@motorola.com>,
	Sumanth Channabasappa <sumanth@CableLabs.com>
Subject: [ipcdn] pktcSigDevToneDbLevel modifying default value and range-Sig
	mib draft-11
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,
        The MIB pktcSigDevToneDbLevel defined in draft-11 has range
(-250..-30) with default value as -40dBm. Normal dial tone is at -13dB
(means -130dBm). Current default value is a too loud signal. I would
recommend to change the defailt to -120 along with the range to
(-250..-110)

MIB description from:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.tx
t

pktcSigDevToneDbLevel    OBJECT-TYPE
         SYNTAX       TenthdBm (-250..-30)
         UNITS        "dBm"=20
         MAX-ACCESS   read-only=20
         STATUS       current=20
         DESCRIPTION=20
             "This MIB Object contains the decibel level for each

              analog signal (tone) that is locally generated =20
              (versus in band supervisory tones) and sourced to =20
              the a-b terminals (TE connection point). Each tone =20
              in itself may consist of multiple frequencies as =20
              defined by the MIB table 'pktcSigDevMultiFreqToneTable'.
   =20
              This MIB Object MUST reflect the desired level at =20
              the Telco (POTS) a-b (T/R) terminals including the =20
              affect of any MTA receiver gain (loss).  This is required=20
              so that locally generated tones are consistent with=20
              remotely generated in band tones at the a-b terminals,=20
              consistent with user expectations.
      =20
              This MIB Object must be set for each tone.
              When tones are formed by combining multi-frequencies,
              the level of each frequency shall be set so as to result
              in the tone level specified in this object at the a-b
              (T/R) terminals.
  =20
              The wide range of levels for this Object is required =20
              to provide signal generator levels across the wide =20
              range of gains (loss) - but does not imply the entire=20
              range is to be achievable given the range of gains (loss)=20
              in the MTA."
       DEFVAL { -40 }=20
       ::=3D{ pktcSigDevMultiFreqToneEntry 8}

Comments please...

Thx, Satish=20


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



From ipcdn-bounces@ietf.org Thu Oct 12 14:06:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GY4w9-0007Q1-7A; Thu, 12 Oct 2006 14:05:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4w7-0007PL-Vl
	for ipcdn@ietf.org; Thu, 12 Oct 2006 14:05:39 -0400
Received: from mms2.broadcom.com ([216.31.210.18])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4w6-00039y-Is
	for ipcdn@ietf.org; Thu, 12 Oct 2006 14:05:39 -0400
Received: from 10.10.64.154 by mms2.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.2)); Thu, 12 Oct 2006 11:05:23 -0700
X-Server-Uuid: 79DB55DB-3CB4-423E-BEDB-D0F268247E63
Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id
	C42FE2AF; Thu, 12 Oct 2006 11:05:22 -0700 (PDT)
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id 9E3772AE; Thu, 12 Oct
	2006 11:05:22 -0700 (PDT)
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.5a-GA) with ESMTP
	id EHK15221; Thu, 12 Oct 2006 11:05:22 -0700 (PDT)
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
	243B720502; Thu, 12 Oct 2006 11:05:22 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] pktcSigDevToneDbLevel modifying default value and
	range-Sig mib draft-11
Date: Thu, 12 Oct 2006 11:05:20 -0700
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F48564024236BD@NT-SJCA-0751.brcm.ad.broadcom.com>
In-Reply-To: <27C82141AA835A428C2EF784424B0D1C054A9304@dlee05.ent.ti.com>
Thread-Topic: [ipcdn] pktcSigDevToneDbLevel modifying default value and
	range-Sig mib draft-11
Thread-Index: AcbuFEtviMz1f0jJRdiqLtEPmiYrRwAE6vzA
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: "Kumar, Satish" <satish.kumar@ti.com>,
	"Ipcdn (E-mail)" <ipcdn@ietf.org>
X-WSS-ID: 69305C692I03880673-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: "Sanchez, Mauricio" <msanchez@ti.com>,
	Freyman Phillip-FPF300 <phillipfreyman@motorola.com>,
	Sumanth Channabasappa <sumanth@CableLabs.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


Satish,

This proposal looks reasonable given the fact that POTS specification
seems to not require a full existing range of (-250, -30). The proposed
default value is also reasonable.

Eugene.

-----Original Message-----
From: Kumar, Satish [mailto:satish.kumar@ti.com]=20
Sent: Thursday, October 12, 2006 8:37 AM
To: Ipcdn (E-mail)
Cc: Sanchez, Mauricio; Freyman Phillip-FPF300; Sumanth Channabasappa
Subject: [ipcdn] pktcSigDevToneDbLevel modifying default value and
range-Sig mib draft-11

Hi,
        The MIB pktcSigDevToneDbLevel defined in draft-11 has range
(-250..-30) with default value as -40dBm. Normal dial tone is at -13dB
(means -130dBm). Current default value is a too loud signal. I would
recommend to change the defailt to -120 along with the range to
(-250..-110)

MIB description from:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.tx
t

pktcSigDevToneDbLevel    OBJECT-TYPE
         SYNTAX       TenthdBm (-250..-30)
         UNITS        "dBm"=20
         MAX-ACCESS   read-only=20
         STATUS       current=20
         DESCRIPTION=20
             "This MIB Object contains the decibel level for each

              analog signal (tone) that is locally generated =20
              (versus in band supervisory tones) and sourced to =20
              the a-b terminals (TE connection point). Each tone =20
              in itself may consist of multiple frequencies as =20
              defined by the MIB table 'pktcSigDevMultiFreqToneTable'.
   =20
              This MIB Object MUST reflect the desired level at =20
              the Telco (POTS) a-b (T/R) terminals including the =20
              affect of any MTA receiver gain (loss).  This is required=20
              so that locally generated tones are consistent with=20
              remotely generated in band tones at the a-b terminals,=20
              consistent with user expectations.
      =20
              This MIB Object must be set for each tone.
              When tones are formed by combining multi-frequencies,
              the level of each frequency shall be set so as to result
              in the tone level specified in this object at the a-b
              (T/R) terminals.
  =20
              The wide range of levels for this Object is required =20
              to provide signal generator levels across the wide =20
              range of gains (loss) - but does not imply the entire=20
              range is to be achievable given the range of gains (loss)=20
              in the MTA."
       DEFVAL { -40 }=20
       ::=3D{ pktcSigDevMultiFreqToneEntry 8}

Comments please...

Thx, Satish=20


_______________________________________________
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 Fri Oct 20 13:40:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GayMH-0007w6-Fr; Fri, 20 Oct 2006 13:40:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GayMG-0007w0-BK
	for ipcdn@ietf.org; Fri, 20 Oct 2006 13:40:36 -0400
Received: from calf.ext.ti.com ([198.47.26.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GayMB-0002p4-1d
	for ipcdn@ietf.org; Fri, 20 Oct 2006 13:40:36 -0400
Received: from dlep34.itg.ti.com ([157.170.170.115])
	by calf.ext.ti.com (8.13.7/8.13.7) with ESMTP id k9KHdTBN032390
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 20 Oct 2006 12:39:39 -0500
Received: from dlep95.itg.ti.com (localhost [127.0.0.1])
	by dlep34.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9KHdNqM012711;
	Fri, 20 Oct 2006 12:39:23 -0500 (CDT)
Received: from dsbe71.ent.ti.com (localhost [127.0.0.1])
	by dlep95.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9KHdNkW024447;
	Fri, 20 Oct 2006 12:39:23 -0500 (CDT)
Received: from dlee05.ent.ti.com ([157.170.170.71]) by dsbe71.ent.ti.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Oct 2006 12:39:23 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Oct 2006 12:38:35 -0500
Message-ID: <27C82141AA835A428C2EF784424B0D1C055B38D9@dlee05.ent.ti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R5 cadence description
Thread-Index: Acb0bpGvKrIGIgRFSv2Crdl3S29vzw==
From: "Kumar, Satish" <satish.kumar@ti.com>
To: "Sumanth Channabasappa" <sumanth@cablelabs.com>,
	"Ipcdn \(E-mail\)" <ipcdn@ietf.org>
X-OriginalArrivalTime: 20 Oct 2006 17:39:23.0677 (UTC)
	FILETIME=[AE6FA4D0:01C6F46E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Freyman Phillip-FPF300 <phillipfreyman@motorola.com>,
	Eugene Nechamkin <enechamkin@broadcom.com>
Subject: [ipcdn] R5 cadence description
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,
	R5 cadence is a non-repeatable cadence. From NCS spec L package
it does not hint so. I would like to add the current modification to MIB
in description text.

Current text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Proposed text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package.
		 This is a non repeatable cadence."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Comments please..

Thx, Satish

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



From ipcdn-bounces@ietf.org Fri Oct 20 15:16:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gazqy-0001Kq-NA; Fri, 20 Oct 2006 15:16:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gazqx-0001Kk-Nu
	for ipcdn@ietf.org; Fri, 20 Oct 2006 15:16:23 -0400
Received: from mms3.broadcom.com ([216.31.210.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gazqw-0003HX-1k
	for ipcdn@ietf.org; Fri, 20 Oct 2006 15:16:23 -0400
Received: from 10.10.64.154 by MMS3.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.2)); Fri, 20 Oct 2006 12:16:11 -0700
X-Server-Uuid: 450F6D01-B290-425C-84F8-E170B39A25C9
Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id
	369DB2AE; Fri, 20 Oct 2006 12:16:11 -0700 (PDT)
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id F34302B0; Fri, 20 Oct
	2006 12:16:10 -0700 (PDT)
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.5a-GA) with ESMTP
	id EIH68622; Fri, 20 Oct 2006 11:51:55 -0700 (PDT)
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
	8492420501; Fri, 20 Oct 2006 11:51:55 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 20 Oct 2006 11:51:53 -0700
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F4856402510554@NT-SJCA-0751.brcm.ad.broadcom.com>
In-Reply-To: <27C82141AA835A428C2EF784424B0D1C055B38D9@dlee05.ent.ti.com>
Thread-Topic: R5 cadence description
Thread-Index: Acb0bpGvKrIGIgRFSv2Crdl3S29vzwACLK0Q
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: "Kumar, Satish" <satish.kumar@ti.com>,
	"Sumanth Channabasappa" <sumanth@cablelabs.com>,
	"Ipcdn (E-mail)" <ipcdn@ietf.org>
X-WSS-ID: 6927FFF12A0893900-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Freyman Phillip-FPF300 <phillipfreyman@motorola.com>
Subject: [ipcdn] RE: R5 cadence description
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


Satish,

The current definition of the PktcRingCadence TC allows for the full
range of signaling patterns, both - repeatable and non-repeatable. All
MIB Objects using the PktcRingCadence TC, are consistently defined in
the MIB draft, and I am not sure if there is any need of making an
exception for the pktcSigDevR5Cadence MIB object. While I agree that
pktcSigDevR5Cadence can have some clarifying statements, I think they
belong to the particular implementation spec (e.g. NCS Specification).

Regards,

Eugene.
=20

-----Original Message-----
From: Kumar, Satish [mailto:satish.kumar@ti.com]=20
Sent: Friday, October 20, 2006 10:39 AM
To: Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Eugene Nechamkin; Freyman Phillip-FPF300
Subject: R5 cadence description

Hi,
	R5 cadence is a non-repeatable cadence. From NCS spec L package
it does not hint so. I would like to add the current modification to MIB
in description text.

Current text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Proposed text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package.
		 This is a non repeatable cadence."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Comments please..

Thx, Satish



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



From ipcdn-bounces@ietf.org Fri Oct 20 17:06:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gb1Z6-00044N-Ed; Fri, 20 Oct 2006 17:06:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb1Z4-000446-VW
	for ipcdn@ietf.org; Fri, 20 Oct 2006 17:06:02 -0400
Received: from bear.ext.ti.com ([192.94.94.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb1Yz-0001UV-FN
	for ipcdn@ietf.org; Fri, 20 Oct 2006 17:06:02 -0400
Received: from dlep34.itg.ti.com ([157.170.170.115])
	by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id k9KL5la9017234
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 20 Oct 2006 16:05:52 -0500
Received: from dlep95.itg.ti.com (localhost [127.0.0.1])
	by dlep34.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9KL5lfS026241;
	Fri, 20 Oct 2006 16:05:47 -0500 (CDT)
Received: from dsbe71.ent.ti.com (localhost [127.0.0.1])
	by dlep95.itg.ti.com (8.13.7/8.13.7) with ESMTP id k9KL5lXQ013295;
	Fri, 20 Oct 2006 16:05:47 -0500 (CDT)
Received: from dlee05.ent.ti.com ([157.170.170.71]) by dsbe71.ent.ti.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Oct 2006 16:05:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Oct 2006 16:05:10 -0500
Message-ID: <27C82141AA835A428C2EF784424B0D1C055B3A8B@dlee05.ent.ti.com>
In-Reply-To: <9C5C578DD43AFD4EA7A9F0BDB2F4856402510554@NT-SJCA-0751.brcm.ad.broadcom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R5 cadence description
Thread-Index: Acb0bpGvKrIGIgRFSv2Crdl3S29vzwACLK0QAATzEfA=
From: "Kumar, Satish" <satish.kumar@ti.com>
To: "Eugene Nechamkin" <enechamkin@broadcom.com>,
	"Sumanth Channabasappa" <sumanth@cablelabs.com>,
	"Ipcdn \(E-mail\)" <ipcdn@ietf.org>
X-OriginalArrivalTime: 20 Oct 2006 21:05:47.0131 (UTC)
	FILETIME=[838CC4B0:01C6F48B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Freyman Phillip-FPF300 <phillipfreyman@motorola.com>
Subject: [ipcdn] RE: R5 cadence description
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 Eugene,
	 PacketCable NCS spec is closed, and changes will be considered
only if very critical and field impacting.  Having said that atleast we
can fix the draft before it becomes RFC. If we leave it as is RFC and
NCS spec  both are broken. Hence I strongly recommend to fix in MIB
description.

Thx, Satish

-----Original Message-----
From: Eugene Nechamkin [mailto:enechamkin@broadcom.com]=20
Sent: Friday, October 20, 2006 12:52 PM
To: Kumar, Satish; Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Freyman Phillip-FPF300
Subject: RE: R5 cadence description


Satish,

The current definition of the PktcRingCadence TC allows for the full
range of signaling patterns, both - repeatable and non-repeatable. All
MIB Objects using the PktcRingCadence TC, are consistently defined in
the MIB draft, and I am not sure if there is any need of making an
exception for the pktcSigDevR5Cadence MIB object. While I agree that
pktcSigDevR5Cadence can have some clarifying statements, I think they
belong to the particular implementation spec (e.g. NCS Specification).

Regards,

Eugene.
=20

-----Original Message-----
From: Kumar, Satish [mailto:satish.kumar@ti.com]
Sent: Friday, October 20, 2006 10:39 AM
To: Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Eugene Nechamkin; Freyman Phillip-FPF300
Subject: R5 cadence description

Hi,
	R5 cadence is a non-repeatable cadence. From NCS spec L package
it does not hint so. I would like to add the current modification to MIB
in description text.

Current text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Proposed text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package.
		 This is a non repeatable cadence."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Comments please..

Thx, Satish



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



From ipcdn-bounces@ietf.org Fri Oct 20 17:12:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gb1fO-0004VI-I8; Fri, 20 Oct 2006 17:12:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb1fN-0004V9-1A
	for ipcdn@ietf.org; Fri, 20 Oct 2006 17:12:33 -0400
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb1fL-0003Dm-MR
	for ipcdn@ietf.org; Fri, 20 Oct 2006 17:12:33 -0400
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.13.7/8.13.7) with ESMTP id k9KLCT5h005543;
	Fri, 20 Oct 2006 15:12:29 -0600 (MDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Oct 2006 15:12:28 -0600
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D8480401D28628@srvxchg.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R5 cadence description
Thread-Index: Acb0bpGvKrIGIgRFSv2Crdl3S29vzwACLK0QAATzEfAAAFGPkA==
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: "Satish Kumar at Texas Instruments" <satish.kumar@ti.com>,
	"Eugene Nechamkin" <enechamkin@broadcom.com>,
	"Ipcdn (E-mail)" <ipcdn@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Freyman Phillip-FPF300 <phillipfreyman@motorola.com>
Subject: [ipcdn] RE: R5 cadence description
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

Satish,

IMHO, unless there is a good technical reason, it would be beyond the
scope of the IPCDN WG.

- S=20

-----Original Message-----
From: Satish Kumar at Texas Instruments=20
Sent: Friday, October 20, 2006 3:05 PM
To: Eugene Nechamkin; Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Freyman Phillip-FPF300
Subject: RE: R5 cadence description

Hi Eugene,
	 PacketCable NCS spec is closed, and changes will be considered
only if very critical and field impacting.  Having said that atleast we
can fix the draft before it becomes RFC. If we leave it as is RFC and
NCS spec  both are broken. Hence I strongly recommend to fix in MIB
description.

Thx, Satish

-----Original Message-----
From: Eugene Nechamkin [mailto:enechamkin@broadcom.com]
Sent: Friday, October 20, 2006 12:52 PM
To: Kumar, Satish; Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Freyman Phillip-FPF300
Subject: RE: R5 cadence description


Satish,

The current definition of the PktcRingCadence TC allows for the full
range of signaling patterns, both - repeatable and non-repeatable. All
MIB Objects using the PktcRingCadence TC, are consistently defined in
the MIB draft, and I am not sure if there is any need of making an
exception for the pktcSigDevR5Cadence MIB object. While I agree that
pktcSigDevR5Cadence can have some clarifying statements, I think they
belong to the particular implementation spec (e.g. NCS Specification).

Regards,

Eugene.
=20

-----Original Message-----
From: Kumar, Satish [mailto:satish.kumar@ti.com]
Sent: Friday, October 20, 2006 10:39 AM
To: Sumanth Channabasappa; Ipcdn (E-mail)
Cc: Eugene Nechamkin; Freyman Phillip-FPF300
Subject: R5 cadence description

Hi,
	R5 cadence is a non-repeatable cadence. From NCS spec L package
it does not hint so. I would like to add the current modification to MIB
in description text.

Current text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Proposed text:
   pktcSigDevR5Cadence     OBJECT-TYPE =20
       SYNTAX       PktcRingCadence =20
       MAX-ACCESS   read-write =20
       STATUS       current =20
       DESCRIPTION =20
           " This object specifies ring cadence 5 (a user defined=20
             field). This object is required for the L line package.
		 This is a non repeatable cadence."=20
       ::=3D { pktcSigDevConfigObjects 10 }

Comments please..

Thx, Satish





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



From ipcdn-bounces@ietf.org Mon Oct 23 18:50:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cb-0002tL-0T; Mon, 23 Oct 2006 18:50:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cM-0002Yn-LE; Mon, 23 Oct 2006 18:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cM-0000Nr-45; Mon, 23 Oct 2006 18:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 17399328DD;
	Mon, 23 Oct 2006 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gc8cL-0004Ov-Te; Mon, 23 Oct 2006 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gc8cL-0004Ov-Te@stiedprstage1.ietf.org>
Date: Mon, 23 Oct 2006 18:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-eventmess-09.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		: Management Event MIB  for PacketCable/IPCablecom MTAs
	Author(s)	: W. De Ketelaere, et al.
	Filename	: draft-ietf-ipcdn-pktc-eventmess-09.txt
	Pages		: 30
	Date		: 2006-10-23
	
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 events generated by PacketCable and IPCablecom compliant 
   Multimedia Terminal Adapter devices.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-09.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-eventmess-09.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-eventmess-09.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-10-23154901.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipcdn-pktc-eventmess-09.txt

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

Content-Type: text/plain
Content-ID: <2006-10-23154901.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 Oct 23 18:51:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc8dL-00062n-Ht; Mon, 23 Oct 2006 18:51:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cq-0004Sx-PW; Mon, 23 Oct 2006 18:50:32 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cq-0000W5-Lz; Mon, 23 Oct 2006 18:50:32 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Gc8cq-0000zU-9j; Mon, 23 Oct 2006 18:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 396622ACD4;
	Mon, 23 Oct 2006 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gc8cL-0004P0-VU; Mon, 23 Oct 2006 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gc8cL-0004P0-VU@stiedprstage1.ietf.org>
Date: Mon, 23 Oct 2006 18:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-signaling-12.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) MIB for
                          PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)
	Author(s)	: G. Beacham, et al.
	Filename	: draft-ietf-ipcdn-pktc-signaling-12.txt
	Pages		: 74
	Date		: 2006-10-23
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-12.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-12.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-12.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-10-23155036.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-10-23155036.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 akstcflabarmnsdgs@flabar.org Sun Oct 29 14:35:52 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GeGRk-00028M-Hq; Sun, 29 Oct 2006 14:35:52 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GeGRk-0004Uj-GT; Sun, 29 Oct 2006 14:35:52 -0500
Received: from 163.209.broadband3.iol.cz ([85.70.209.163] helo=duron-1300)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GeGRg-0002uS-9K; Sun, 29 Oct 2006 14:35:51 -0500
Received: from 199.44.15.99 (HELO mailgw1.flabar.org)
     by lists.ietf.org with esmtp (STMX6NFG Y0PK6R)
     id A57355-P9TSSR-QV
     for ipcdn-archive@lists.ietf.org; Sun, 29 Nov 2006 19:35:46 -0060
From: "Cindy Whalen" <CindyWhalen@flabar.org>
To: <ipcdn-archive@lists.ietf.org>
Subject: pain spot Non-uralian
Date: Sun, 29 Nov 2006 19:35:46 -0060
Message-ID: <01c6fb91$6dff10a0$6c822ecf@akstcflabarmnsdgs>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Importance: Normal
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4

approbation in terms warm enough to satisfy her feelings, though she talked to bingley of nothing elseelizabeth found the interest of the subject increase, and listened with all her heart; but the



From akstcdynastymnsdgs@dynasty.net Tue Oct 31 19:02:14 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gf3Yb-0001yB-CZ; Tue, 31 Oct 2006 19:02:13 -0500
Received: from adsl196-198-223-206-196.adsl196-7.iam.net.ma ([196.206.223.198] helo=elkholti-iin86q)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gf3YT-0003bF-KP; Tue, 31 Oct 2006 19:02:13 -0500
Received: from 208.252.179.200 (HELO relay.cisp.com)
     by lists.ietf.org with esmtp (4QIUYTEX4NJA W2L1)
     id GC4R36-O92YDR-ER
     for ipcdn-archive@lists.ietf.org; Wed, 1 Dec 2006 00:02:07 0000
Date:	Wed, 1 Dec 2006 00:02:07 0000
From:	"Arlene Hubbard" <akstcdynastymnsdgs@dynasty.net>
X-Mailer: The Bat! (v1.46d) Business
X-Priority: 3 (Normal)
Message-ID: <795383472.60082596194730@thebat.net>
To: ipcdn-archive@lists.ietf.org
Subject: My dear
MIME-Version: 1.0
Content-Type: text/plain;
  charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-Spam: Not detected
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

Red Reef Labs For New Manufacturing and Distribution Contract Iwn China!

Compzany red Reef Laboratowries Inc.
STOCK: RREF
Price: $0.55
Recommendation: STR ONG B UY 

RREF has just agrneed to the terms of a new manufacturing and distribution 
contract for BioClear(tm)FF. With all the nfews on RREF and it expansions 
as well as new applicatons for its prodjucts we expect to see more of this 
type of contract going in place and expandng the market for this innzovative 
companby.

RREF is pricded to buy and holding a steady price. We believe with news like 
this and up coming announcemenrts of more contracts and the soon to be 
established lab facilities in Louisoiana and the upcoming satellite labs that this 
stwocks pricee will bring great returns for its inzvestors.

Get on RREF Wednesday, November 1, 2006

I hope it was a helper.I'll email you later this week.

Arlene Hubbard.

"an easy distance, do you call it? it is nearly fifty miles."
before they  did. as the day of his arrival drew near:"the engagement between them is of a peculiar kind. from their infancy, they have been
"oh dear!-yes-certainly. i am sure lizzy will be very happy-i am sure she can have no objection.



