From estrellastein@americaneagle.com Sat Jun 03 11:47:17 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmYLM-0002TB-Vf for ipcdn-archive@lists.ietf.org; Sat, 03 Jun 2006 11:47:16 -0400 Received: from [62.29.140.66] (helo=BABY) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmYLK-0007MN-MK for ipcdn-archive@lists.ietf.org; Sat, 03 Jun 2006 11:47:16 -0400 Message-Id: <002001c6871a$c293bf80$64d500d3@kttkiyo> From: "celestyn easley" To: "melly fitzgerald" Subject: Need cash, moss-brown Date: Sat, 03 Jun 2006 10:41:51 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0020_01C6871A.C293BF80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 4.1 (++++) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 This is a multi-part message in MIME format. ------=_NextPart_000_0020_01C6871A.C293BF80 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable How much are you paying for your Home? To much?=20 You have been pre-approved to fill out for a ref inance laon,=20 if you need some cash to spend ANY way you like, or simply wish=20 to LOWER your monthly payments by a third or more, etc. We skip the middle man to save hundreds with deals we have!=20 This offer is for you, we DONT CARE about your credit.=20 Apply online now for your instant quote. Stop over paying...=20 http://bayanmc.org/d2/ wild cherry sprinkler system ginger wine river novel ground fir on-glide re-engagement sea cabbage generator gas shoe dealer Johnny verde yellow-sallow plume moth self-pityingly ring necrosis Unuk al hay pernyi silkworm late-kissed all-judging poor-debtor law ring-chain tautomerism drizzle-drozzle cotton wilt sand dab sea bank boot ironer culture fluid physic nut ever-increasing fancy-raised bottle soaker ------=_NextPart_000_0020_01C6871A.C293BF80 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

How much are you paying for your Home? To much?
You have been pre-approved to fill out for a ref inance laon,
if you need some cash to spend ANY way you like, or simply wish
to LOWER your monthly payments by a third or more, etc.

We skip the middle man to save hundreds with deals we have!
This offer is for you, we DONT CARE about your credit.

Apply online now for your instant quote. Stop over paying...

http://bayanmc.org/d2/

wild cherry sprinkler system ginger wine river novel ground fir
on-glide re-engagement
sea cabbage generator gas shoe dealer Johnny verde yellow-sallow plume moth=
self-pityingly ring necrosis Unuk al hay pernyi silkworm late-kissed
all-judging poor-debtor law ring-chain tautomerism
drizzle-drozzle cotton wilt sand dab
sea bank boot ironer culture fluid physic nut ever-increasing
fancy-raised bottle soaker

= ------=_NextPart_000_0020_01C6871A.C293BF80-- From ipcdn-bounces@ietf.org Wed Jun 14 15:50:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqbNR-00057N-BJ; Wed, 14 Jun 2006 15:50:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqbNK-00054r-BO; Wed, 14 Jun 2006 15:50:02 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqbNJ-00014w-Tm; Wed, 14 Jun 2006 15:50:02 -0400 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 k5EJo1WR030748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jun 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FqbNJ-0006sE-Kv; Wed, 14 Jun 2006 15: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: Date: Wed, 14 Jun 2006 15:50:01 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: ipcdn@ietf.org Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-signaling-11.txt X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-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-11.txt Pages : 71 Date : 2006-6-14 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-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-pktc-signaling-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-pktc-signaling-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-6-14112631.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-pktc-signaling-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-14112631.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 Fri Jun 16 10:34:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrFPD-0000iq-IN; Fri, 16 Jun 2006 10:34:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrFPC-0000il-7w for ipcdn@ietf.org; Fri, 16 Jun 2006 10:34:38 -0400 Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrFPA-0002Mz-Ok for ipcdn@ietf.org; Fri, 16 Jun 2006 10:34:38 -0400 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.13.6/8.13.6) with ESMTP id k5GEYZ5U015008 for ; Fri, 16 Jun 2006 08:34:36 -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 Subject: [ipcdn] WGLC on draft-ietf-ipcdn-pktc-signaling-11.txt to end July 1st 2006 Date: Fri, 16 Jun 2006 08:34:35 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ipcdn] WGLC on draft-ietf-ipcdn-pktc-signaling-11.txt to end July 1st 2006 Thread-Index: AcaP68+fwbfnjLoQQ7qQONaSPjyJBgBZbMrw From: "Jean-Francois Mule" To: X-Approved: ondar X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org Folks, Rich and I would like to start a final WGLC last call on this ID given that the initial WGLC was done in 2004 and the draft has evolved since then. Please send your comments to the authors and the ipcdn list by July 1st 2006. Rich and Jean-Francois. IPCDN co-chairs. > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Wednesday, June 14, 2006 1:50 PM > To: i-d-announce@ietf.org > Cc: ipcdn@ietf.org > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-signaling-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. >=20 > 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-11.txt > Pages : 71 > Date : 2006-6-14 >=20 > 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. >=20 > 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. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling- > 11.txt >=20 > 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. >=20 >=20 > 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-11.txt". >=20 > 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 >=20 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.txt". >=20 > 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. >=20 >=20 > 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 Fri Jun 16 10:44:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrFYG-0005yV-Uq; Fri, 16 Jun 2006 10:44:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrFYG-0005yQ-0Z for ipcdn@ietf.org; Fri, 16 Jun 2006 10:44:00 -0400 Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrFYE-00033n-Lw for ipcdn@ietf.org; Fri, 16 Jun 2006 10:43:59 -0400 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.13.6/8.13.6) with ESMTP id k5GEhuTv016755; Fri, 16 Jun 2006 08:43:57 -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 Subject: [ipcdn] No meeting planned in IETF#66 Date: Fri, 16 Jun 2006 08:43:56 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ipcdn] No meeting planned in IETF#66 Thread-Index: AcaP68+fwbfnjLoQQ7qQONaSPjyJBgBZllpg From: "Jean-Francois Mule" To: X-Approved: ondar X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: "Richard Woundy @ Comcast" X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org We have 2 milestones left in our wg charter: 1/ draft-ietf-ipcdn-pktc-signaling=20 It is in WGLC. 2/ draft-ietf-ipcdn-pktc-eventmess After a discussion with the editor, pending the upcoming draft update, most (if not all) of the open issues raised on the list will be addressed. Given the above status of the drafts and the silence on new open issues, it appears a WG meeting is not required at the next IETF. Let Rich and myself know if you any questions on the above. Jean-Francois. _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Fri Jun 16 11:36:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrGMm-0005Ws-LA; Fri, 16 Jun 2006 11:36:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrGMk-0005Va-Iv for ipcdn@ietf.org; Fri, 16 Jun 2006 11:36:10 -0400 Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrGMk-0007Fy-45 for ipcdn@ietf.org; Fri, 16 Jun 2006 11:36:10 -0400 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.13.6/8.13.6) with ESMTP id k5GFa832029830 for ; Fri, 16 Jun 2006 09:36:09 -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, 16 Jun 2006 09:36:08 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Changes to draft-ietf-ipcdn-pktc-signaling-11 Thread-Index: AcaP68+fwbfnjLoQQ7qQONaSPjyJBgBZbMrwAAIdfLA= From: "Sumanth Channabasappa" To: X-Approved: ondar X-Spam-Score: 0.0 (/) X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9 Subject: [ipcdn] Changes to draft-ietf-ipcdn-pktc-signaling-11 X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org Folks, Find enclosed the changes incorporated into "draft-ietf-ipcdn-pktc-signaling" (http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-11. txt). regards Sumanth Change #1/3: New MIB Object ----------- > Rationale: Excerpts from the email sent by Phillip Freyman to the IPCDN reflector (dated 3/29) > Proposed addition pktcSigDevrpAsDtsDuration OBJECT-TYPE=20 SYNTAX Unsigned32 (0|200..500)=20 UNITS "Milliseconds"=20 MAX-ACCESS read-write=20 STATUS current=20 DESCRIPTION=20 " This object specifies the duration of the rpASDTS ring pulse prior to the start of the transmission of the=20 FSK or DTMF containing the Caller ID information. It is =20 only used when 'pktcSigDevCidMode' is set to a value of=20 'rpAsETS'.=20 The following table defines the default values for this MIB Object, depending on the signal type=20 (pktcSigDevCidMode) and MUST be followed: Value of 'pktcSigDevCidMode' Default value duringringingETS 0 (not used) dtAsETS 0 (not used) rpAsETS 250=20 lrAsETS 0 (not used) lrETS 0 (not used) An attempt to set this object while the value of=20 pktcSigDevCidMode is not 'rpAsETS' will result in=20 an 'inconsistent value' error."=20 REFERENCE =20 "ETSI-EN-300-659-1 Specification and Belgacom=20 BGC_D_48_9811_30_09_EDOC version 3.3"=20 DEFVAL { 250 }=20 ::=3D {pktcSigDevConfigObjects 41 }=20 =20 Change #2/3: Modifications to existing MIB Objects ----------- =20 > Rationale: Comments from Randy Presuhn (3/30, 3/31), Richard Woundy (3/30, 3/31) and Phillip Freyman (3/31) and offline discussions between authors and primary contributors > Changes were affected to: pktcSigPulseSignalRepeatCount =20 pktcSigDevCidAfterRing =20 pktcSigDevCidAfterDTAS =20 pktcSigDevCidAfterRPAS =20 pktcSigDevRingAfterCID =20 pktcSigDevCidDTASAfterLR =20 pktcSigDevVmwiAfterDTAS =20 pktcSigDevVmwiAfterRPAS =20 pktcSigDevVmwiDTASAfterLR =20 pktcSigDevCidDelayAfterLR =20 pktcSigDevVmwiDelayAfterLR =20 pktcSigDevrpAsDtsDuration =20 Note: - A default value of '0' was chosen in all cases (or a range of 0-0 in=20 the first mentioned object) - A clarification was provided to indicate when a MIB Object is used E.g.=20 pktcSigDevCidAfterRing =20 =20 It is only used when pktcSigDevCidMode is set to a value of =20 'duringRingingETS' - A normative requirement was added to follow table descriptions for=20 default values.=20 E.g. pktcSigDevCidAfterRing =20 The following table defines the default values for this MIB Object, depending on the signal type=20 (pktcSigDevCidMode) and MUST be followed: Value of 'pktcSigDevCidMode' Default value duringringingETS 550 ms dtAsETS 0 (not used) rpAsETS 0 (not used) lrAsETS 0 (not used) lrETS 0 (not used) =20 Change #3/3: Editorial and other changes ----------- - Added the new MIB OBject to the MIB group 'pktcInternationalGroup' - Corrected the incorrect reference to 'pktcSigDevCidMode' in=20 pktcSigDevVmwiDelayAfterLR=20 - correct reference 'pktcSigDevVmwiDelayAfterLR' - Updated the draft details (date etc) - other minor editorials Changes as per Rich Woundy's comments (thanks!) ---------------------------------------------- - Updated references for pktcSigDevCidDtmfStartCode, pktcSigDevCidDtmfEndCode, pktcSigDevVmwiDtmfStartCode, and pktcSigDevVmwiDtmfEndCode from "[ETSI-EN.*]" to "ETSI-EN.* specification" - Removed 'NOT RECOMMENDED' from list of keywords - Updated RFC 3291 to RFC 4001 (and removed note regarding " Date: Mon, 19 Jun 2006 15:50:02 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: ipcdn@ietf.org Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-eventmess-06.txt X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-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-06.txt Pages : 30 Date : 2006-6-19 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. 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-eventmess-06.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-06.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-06.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-6-19131257.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-pktc-eventmess-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-pktc-eventmess-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-19131257.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 Jun 19 16:31:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQOj-0004BS-UK; Mon, 19 Jun 2006 16:31:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsPqN-0005Eg-7R for ipcdn@ietf.org; Mon, 19 Jun 2006 15:55:31 -0400 Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsPqJ-0001eJ-9r for ipcdn@ietf.org; Mon, 19 Jun 2006 15:55:29 -0400 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.13.6/8.13.6) with ESMTP id k5JJtQd0023322 for ; Mon, 19 Jun 2006 13:55:26 -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: Mon, 19 Jun 2006 13:55:26 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Changes incorporated in draft-ietf-ipcdn-pktc-eventmess-06.txt Thread-Index: AcaT2nBrjDDiYDSeRgGqpyTCojrv0A== From: "Sumanth Channabasappa" To: X-Approved: ondar X-Spam-Score: 0.0 (/) X-Scan-Signature: 64592953d6410e1f725ee21266e2f396 Subject: [ipcdn] Changes incorporated in draft-ietf-ipcdn-pktc-eventmess-06.txt X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org Folks, This is to inform you all that 'draft-ietf-ipcdn-pktc-eventmess-06.txt' is now available (http://www.ipcdn.org/drafts/draft-ietf-ipcdn-pktc-eventmess-06.txt).=20 The changes incorporated in this draft are enclosed in this email as an FYI. Regards Sumanth Note: Changes #1 and #7 are new. Remaining are mostly a repeat of the changes suggested by Eugene in the email dated 3/29 to the IPCDN mailing list. However, please verify all changes. =20 Change #1/8: --------- - Removed the MIB Object 'pktcDevEvReportingLevel' =20 Reasoning: This MIB Object affected other MIB Objects and the behavior when the affected MIB Objects and the MIB Object in=20 question were set in the same SNMP PDU resulted in complications. =20 Further, attempts to handle such side-effects lead to non-trivial requirements that would make for a complex MIB Object. =20 Given that the advantage of this MIB Object was to make it easy to=20 set values across 'Event Classes' and was not required for the=20 MIB to operate, this 'nice-to-have' MIB Object has been removed. =20 Further, this changes the index of 'pktcDevEventClassReportTable' from 'pktcDevEventControl 6' to ' pktcDevEventControl 5' =20 =20 Change #2/8: References --------- =20 Added the following new references: =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 =20 - J. Postel, "User Datagram Protocol", STD0006, RFC 768 - to be refered to by section 3.6. =20 - C. Lonvick, "The BSD syslog Protocol", RFC 3164, August 2001 - to be reffered to by some MIB Objects. =20 =20 Updated the following references: =20 - [PKT-SP-PROV], [PKT-SP-MGCP], [PKT-SP-CODEC] to reflect current documents =20 =20 =20 Change #3/8: --------- Renamed the following MIB Objects to stay consistant in terminology with RFC3164 ("BSD Syslog protocol"): =20 pktcDevEvReportingLevel -> pktcDevEvSeverityLevel =20 pktcDevEventClassReportLevel -> pktcDevEventClassSeverityLevel =20 pktcDevEventDescrLevel -> pktcDevEventDescrSeverityLevel =20 =20 Change #4/8: --------- =20 Introduced new textual convention: SeverityLevel =20 SeverityLevel - to simplify the syntax for pktcDevEvSeverityLevel, pktcDevEventClassSeverityLevel, and pktcDevEventDescrSeverityLevel=20 =20 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 } =20 =20 Change #5/8: --------- The DESCRIPTION and/or SYNTAX clause of certain MIB Objects were updated, as listed below:=20 =20 pktcDevEvControl: DECSRIPTION clause has been modified to clarify the behavior of the MTA when resetEventLogTable(0) bit is set.=20 =20 DESCRIPTION =20 "This MIB object defines the actions related to the event=20 log configuration.=20 =20 The MTA MUST take the appropriate action whenever=20 a bit is set to a value of '1'.=20 =20 Setting the resetEventLogTable(0) bit to a value of '1' - deletes all entries in pktcDevEventLogTable, - resets the value of pktcDevEvLogIndex to '0' =20 Setting resetEventDescrTable(1) to a value of '1' - resets the pktcDevEventDescrTable to the factory default values. =20 Setting a control bit to a value of '0' MUST not result in any action.=20 =20 Reading this MIB object MUST always return '00'. MTA MUST perform the same actions regardless of=20 persistentance (i.e. storage in non-volatile memory)." =20 =20 =20 pktcDevEventClassReportEntry - DECSRIPTION modified to require a 'generic' event class when a vendor does not support multiple event classes: DESCRIPTION "An entry in this table MUST be created for each=20 event class defined by a vendor for the events described as part of 'pktcDevEventDescrTable'. =20 If an MTA vendor does not define event classes, then MTA MUST create one entry for the event=20 class 'generic'." =20 =20 PktcDevEventClassReportEntry - modified to reflect the textual conventions defined for: pktcDevEventClass and pktcDevEventClassSeverityLevel: =20 PktcDevEventClassReportEntry::=3D SEQUENCE { pktcDevEventClass SnmpAdminString, pktcDevEventReportStatus TruthValue, pktcDevEventClassSeverityLevel SeverityLevel } =20 =20 pktcDevEventClass: - DESCRIPTION clause modified to clarify the usage: =20 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." =20 PktcDevEventDescrEntry - modified to use new SYNTAX for two objects: pktcDevEventDescrSeverityLevel and pktcDevEventDescrClass: PktcDevEventDescrEntry::=3D SEQUENCE { pktcDevEventDescrId Unsigned32, pktcDevEventDescrEnterprise Unsigned32, pktcDevEventDescrFacility INTEGER, pktcDevEventDescrSeverityLevel SeverityLevel, pktcDevEventDescrReporting BITS, pktcDevEventDescrText SnmpAdminString, pktcDevEventDescrClass SnmpAdminString } =20 =20 =20 pktcDevEventDescrClass: - MAX-ACCESS changed to "read-only" to avoid cross-reference consistency complications with pktcDevEventClassReportTable. =20 =20 pktcDevEventLogTable - the following added to the end of the DESCRIPTION clause: "The contents of this table MAY persist in non-volatile memory." =20 pktcDevEvLogCorrelationId:=20 - the following clarification was added to the end of the =20 DECRIPTION clause: "Although a 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 a persistent=20 pktcDevEventLogTable." =20 - REFERENCE clause added: REFERENCE "PacketCable MTA Device Provisioning Specification,=20 [PKT-SP-PROV]." =20 =20 pktcDevEvLogAdditionalInfo - the following clarification was added to the DESCRIPTION clause: "If MTA cannot provide any additional=20 information for the particular event generated, it MUST=20 populate this MIB Object with a string of zero-length." =20 =20 Change #6/8: --------- Updated references, as indicated to the following MIB Objects; =20 =20 > REFERENCE "RFC 3164, The BSD syslog Protocol, [RFC3164]." =20 was added to: =20 pktcDevEvLogTime, pktcDevEventClassSeverityLevel, pktcDevEvSyslogAddress, pktcDevEvSyslogUdpPort, pktcDevEvSeverityLevel, pktcDevEventDescrFacility, pktcDevEventDescrSeverityLevel =20 =20 =20 > REFERENCE "PacketCable MTA Device Provisioning Specification,=20 [PKT-SP-PROV]." =20 added to: =20 pktcDevEvSyslogAddressType, pktcDevEvSyslogAddress, pktcDevEventDescrId =20 =20 > REFERENCE "PacketCable MTA Device Provisioning Specification,=20 [PKT-SP-PROV]; added to: =20 pktcDevEvSyslogAddress, pktcDevEventDescrId =20 =20 > REFERENCE "PacketCable Management Event Mechanism Specification, [PKT-SP-MEM1.5];" added to: pktcDevEventDescrId=20 =20 =20 Change #7/8:=20 -----------=20 The size of the index 'pktcDevEventClass' and the MIB Object 'pktcDevEventDescrClass' was increased to 1..100 to allow for=20 descriptive event class names =20 =20 Change #8/8: Misc. changes --------- > Updated author's addresses > Updated date/time > Updated MIB details to align with the MTA and Sig drafts > Removed 'NOT RECOMMENDED' from list of keywords > Fixed non-ASCII characters present in the document > Removed unused references ([RFC821], [RFC2026], [RFC1034], [RFC3550]) =20 =20 =20 =20 MIB compliation output from ' smilint@ibr.cs.tu-bs.de': ------------------------------------------------------ =20 smilint -m -s -e -l 6 PKTC-IETF-EVENT-MIB =20 PKTC-IETF-EVENT-MIB:71: [2] {bad-identifier-case} `XXX' should start with a lower case letter PKTC-IETF-EVENT-MIB:71: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element =20 =20 ID-nits output from http://tools.ietf.org/tools/idnits/idnits.pyht: ------------------------------------------------------------------ =20 idnits 1.102=20 =20 tmp/draft-ietf-ipcdn-pktc-eventmess-06.txt: =20 =20 Checking nits according to http://www.ietf.org/ID-Checklist.html: =20 Checking conformance with RFC 3978/3979 boilerplate... =20 the boilerplate looks good. =20 No nits found. =20 Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: Nothing found here (but these checks do not cover all of 1id-guidelines.txt yet). =20 Miscellaneous warnings: None. =20 Experimental warnings: None. =20 No nits found. =20 _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Mon Jun 26 15:15:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuwYq-0006up-Rs; Mon, 26 Jun 2006 15:15:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuwYm-0006mb-QX; Mon, 26 Jun 2006 15:15:48 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuwYk-0004KZ-HM; Mon, 26 Jun 2006 15:15:48 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k5QJFkUt023326; Mon, 26 Jun 2006 12:15:46 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k5QJFkDb023325; Mon, 26 Jun 2006 12:15:46 -0700 Date: Mon, 26 Jun 2006 12:15:46 -0700 Message-Id: <200606261915.k5QJFkDb023325@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org Subject: [ipcdn] RFC 4546 on Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4546 Title: Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces Author: D. Raftus, E. Cardona Status: Standards Track Date: June 2006 Mailbox: david.raftus@ati.com, e.cardona@cablelabs.com Pages: 139 Characters: 300844 Obsoletes: RFC2670 See-Also: I-D Tag: draft-ietf-ipcdn-docs-rfmibv2-14.txt URL: http://www.rfc-editor.org/rfc/rfc4546.txt 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 set of managed objects for Simple Network Management Protocol (SNMP) based management of the Radio Frequency (RF) interfaces for systems compliant with the Data Over Cable Service Interface Specifications (DOCSIS). [STANDARDS TRACK] This document is a product of the IP over Cable Data Network Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Tue Jun 27 16:00:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvJjS-00035W-TP; Tue, 27 Jun 2006 16:00:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvJa3-0007S5-82; Tue, 27 Jun 2006 15:50:39 -0400 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 1FvJa2-0001Qy-UO; Tue, 27 Jun 2006 15:50:39 -0400 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 k5RJo3UA002957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Jun 2006 19:50:04 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FvJZT-0005Jb-63; Tue, 27 Jun 2006 15:50:03 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 27 Jun 2006 15:50:03 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: ipcdn@ietf.org Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-eventmess-07.txt X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-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-07.txt Pages : 30 Date : 2006-6-27 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-07.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-07.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-07.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-6-27145735.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-pktc-eventmess-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-pktc-eventmess-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-27145735.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 Thu Jun 29 07:52:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fvv4E-0002Gm-1L; Thu, 29 Jun 2006 07:52:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fvv4D-0002Bt-2q for ipcdn@ietf.org; Thu, 29 Jun 2006 07:52:17 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fvv4C-0002md-IX for ipcdn@ietf.org; Thu, 29 Jun 2006 07:52:17 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k5TBmusD016316 for ; Thu, 29 Jun 2006 07:48:56 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] WGLC on draft-ietf-ipcdn-pktc-signaling-11.txt to end July1st 2006 Date: Thu, 29 Jun 2006 14:52:11 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ipcdn] WGLC on draft-ietf-ipcdn-pktc-signaling-11.txt to end July1st 2006 Thread-Index: AcaP68+fwbfnjLoQQ7qQONaSPjyJBgBZbMrwAoKE4LA= From: "Romascanu, Dan $Dan$" To: "Jean-Francois Mule" , X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee Cc: X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org I did not perform a full MIB Doctor review, here are some comments from a partial review: 1. The title of the document includes twice the word 'signaling' - is this necessary?=20 2. idnits complains about un-used references:=20 - Unused Reference: 'ETSI-TS-101-909-4' is defined on line 3335, but not referenced ' [ETSI-TS-101-909-4] ETSI TS 101 909-4:"Access and Terminals (AT);' - Unused Reference: 'ETSI-EN-300-324-1' is defined on line 3354, but not referenced ' [ETSI-EN-300-324-1] ETSI EN 300 324-1 V2.1.1 (2000-04):"V Interfaces' 3. No need for the second paragraph in the Abstract. Anyway, this is repeated in a 'boilerplate standard' manner in the Introduction section. 4. I believe that the following statement is confusing: This MIB module also utilizes the syntax definition of the=20 Differentiated Services Code Point (DSCP) from DIFFSERV-DSCP-TC=20 [RFC3289] for signaling MIB objects to allow for differentiation=20 between various types of traffic in the service provider network.=20 I would rather replace it with: This MIB module also utilizes the syntax definition of the=20 Differentiated Services Code Point (DSCP) TC from DIFFSERV-DSCP-TC=20 [RFC3289] for defining MIB objects that allow for differentiation=20 between various types of traffic in the service provider network.=20 5. I could not understand what is meant by: This MIB module also utilizes SNMP management MIB architecture from=20 SNMP-FRAMEWORK-MIB [RFC3411].=20 6. pktcSigNotification=20 =20 pktcSigNotification - this object is used for signaling notification=20 and reserved for future use.=20 This is not an object, but just an OID. Needs not any explanation 7. DESCRIPTION clause of pktcSigDevSilenceSuppression " This object specifies if the device is capable of=20 silence suppression (Voice Activity Detection)." =20 Better say:=20 " This object specifies if the device is capable of=20 silence suppression (as result of Voice Activity Detection)." =20 8. DESCRIPTION clause of pktcSigDevCidSigProtocol =20 "This object identifies the subscriber line protocol used=20 for signaling on-hook caller id information. Different=20 countries define different caller id signaling protocols to=20 support caller identification. Frequency shift keying (FSK)=20 is most commonly used. Dual tone multi-frequency (DTMF)=20 is an alternative."=20 This object has a MAX-ACCESS clause of read-write. The DESCRIPTION should rather say: "This object is used to configure the subscriber line protocol used=20 for signaling on-hook caller id information. Different=20 countries define different caller id signaling protocols to=20 support caller identification.=20 - setting this object at a value fsk(1) sets the subscriber line protocol=20 to be Frequency Shift Keying (FSK)=20 - setting this object at a value dtmf(2) sets the subscriber line protocol=20 to be Dual tone multi-frequency (DTMF)."=20 9. I believe that pktcSignalingVersion has a significance only for pktcSignalingType ncs(3). If true, this needs to be mentioned in the object DESCRIPTION clause.=20 10. It is not clear what value reserved(2) means in the PktcSigType TC. 'for future use' does not make too much sense, if this value will become meaningful in the future you cannot change the semantics of this enumerated value. I suggest to skip this value and use only other and ncs 11. It is not clear what level of interoperability can the pktcSignalingVendorExtension object offer if the encoded string is vendor specific. I suggest to take this oibject out.=20 12. It does not make sense to specify DEFVAL clauses for read-only objects (pktcSigDefNcsReceiveUdpPort, pktcSigPowerRingFrequency). If configuration by SNMP is not allowed, setting the instrumentation at the desired state has not any relation with the SNMP agent.=20 13. Inconsistent use of keywords in the DESCRIPTION clause of pktcSigDevToneDbLevel. Actually I believe that there is no place here for a MUST. Instead of 'This MIB Object MUST reflect the desired level...' rather say 'This MIB object reflects ...' 14. In several places the term 'SNMP Management Station' is being used. I prefer 'SNMP Manager application'.=20 Dan > -----Original Message----- > From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]=20 > Sent: Friday, June 16, 2006 5:35 PM > To: ipcdn@ietf.org > Subject: [ipcdn] WGLC on=20 > draft-ietf-ipcdn-pktc-signaling-11.txt to end July1st 2006 >=20 > Folks, >=20 > Rich and I would like to start a final WGLC last call on=20 > this ID given that the initial WGLC was done in 2004 and the=20 > draft has evolved since then. >=20 > Please send your comments to the authors and the ipcdn=20 > list by July 1st 2006. >=20 > Rich and Jean-Francois. > IPCDN co-chairs. >=20 > > -----Original Message----- > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > Sent: Wednesday, June 14, 2006 1:50 PM > > To: i-d-announce@ietf.org > > Cc: ipcdn@ietf.org > > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-signaling-11.txt > >=20 > > A New Internet-Draft is available from the on-line Internet-Drafts=20 > > directories. > > This draft is a work item of the IP over Cable Data Network Working=20 > > Group of the IETF. > >=20 > > 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-11.txt > > Pages : 71 > > Date : 2006-6-14 > >=20 > > This memo defines a portion of the Management Information=20 > Base (MIB)=20 > > for use with network management protocols in the Internet community. > > In particular, it provides a common data and format=20 > representation for=20 > > PacketCable and IPCablecom compliant Multimedia Terminal Adapter=20 > > devices. > >=20 > > This memo specifies a MIB module in a manner that is=20 > compliant to the=20 > > SNMP SMIv2. The set of objects are consistent with the=20 > SNMP framework=20 > > and existing SNMP standards. > >=20 > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling- > > 11.txt > >=20 > > To remove yourself from the I-D Announcement list, send a=20 > message to=20 > > i-d-announce-request@ietf.org with the word unsubscribe in=20 > the body of=20 > > the message. > > You can also visit=20 > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > >=20 > >=20 > > Internet-Drafts are also available by anonymous FTP. Login with the=20 > > username "anonymous" and a password of your e-mail address. After=20 > > logging in, type "cd internet-drafts" and then > > "get draft-ietf-ipcdn-pktc-signaling-11.txt". > >=20 > > A list of Internet-Drafts directories can be found in=20 > > http://www.ietf.org/shadow.html or=20 > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >=20 > >=20 > > Internet-Drafts can also be obtained by e-mail. > >=20 > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-ipcdn-pktc-signaling-11.txt". > >=20 > > 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=20 > 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. > >=20 > >=20 > > Below is the data which will enable a MIME compliant mail reader=20 > > implementation to automatically retrieve the ASCII version of the=20 > > Internet-Draft. >=20 >=20 > _______________________________________________ > IPCDN mailing list > IPCDN@ietf.org > https://www1.ietf.org/mailman/listinfo/ipcdn >=20 _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Fri Jun 30 18:52:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwRqB-00082e-Sk; Fri, 30 Jun 2006 18:51:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwRq8-0007yK-La; Fri, 30 Jun 2006 18:51:56 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwRq4-0007v6-E4; Fri, 30 Jun 2006 18:51:56 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k5UMpqqT010214; Fri, 30 Jun 2006 15:51:52 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k5UMpp5s010213; Fri, 30 Jun 2006 15:51:51 -0700 Date: Fri, 30 Jun 2006 15:51:51 -0700 Message-Id: <200606302251.k5UMpp5s010213@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org Subject: [ipcdn] RFC 4547 on Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ipcdn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4547 Title: Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems Author: A. Ahmad, G. Nakanishi Status: Standards Track Date: June 2006 Mailbox: azlina@cisco.com, gnakanishi@motorola.com Pages: 40 Characters: 83917 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipcdn-docsisevent-mib-06.txt URL: http://www.rfc-editor.org/rfc/rfc4547.txt 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 Simple Network Management Protocol (SNMP) based event notification management of Data Over Cable Service Interface Specification (DOCSIS) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Cable Device MIB. This memo specifies a MIB module in a manner that is compliant to the Structure of Management Information Version 2 (SMIv2). The set of objects is consistent with the SNMP framework and existing SNMP standards. [STANDARDS TRACK] This document is a product of the IP over Cable Data Network Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn