headers
Internet-Drafts | 18 Aug 2008 05:45
Picon
Favicon

I-D Action:draft-ietf-ipcdn-pktc-eventmess-14.txt

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

	Title           : Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices
	Author(s)       : S. Channabasappa, I. Property
	Filename        : draft-ietf-ipcdn-pktc-eventmess-14.txt
	Pages           : 38
	Date            : 2008-08-17

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 management of events that 
can be generated by PacketCable- and IPCablecom-compliant Multimedia 
Terminal Adapter devices. 

 

 

 

 

De Ketelaere/Nechamkin/Channabasappa Expires - February 2009  [page 1] 

PacketCable/IPCablecom Event management MTA MIB

August 2008
(Continue reading)

Permalink | Reply |
headers
Wijnen, Bert (Bert | 9 Mar 2006 06:41
Picon
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt

On IESG agenda for March 16 now.

Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy <at> cable.comcast.com]
> Sent: Monday, March 06, 2006 16:18
> To: ipcdn <at> ietf.org
> Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
> 
> 
> Folks,
> 
> This is the draft version I promised to post on Friday at 5pm ET, per
> <http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01876.html>.
> 
> -- Rich
> 
> -----Original Message-----
> From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org] 
> Sent: Monday, March 06, 2006 2:50 AM
> To: i-d-announce <at> ietf.org
> Cc: ipcdn <at> ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the IP over Cable 
> Data Network
> Working Group of the IETF.
(Continue reading)

Permalink | Reply |
headers
Woundy, Richard | 6 Mar 2006 16:18
Picon

RE: I-D ACTION:draft-ietf-ipcdn-device-mibv2-11.txt

Folks,

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

-- Rich

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

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

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

Permalink | Reply |
headers
Eugene Nechamkin | 16 Dec 2005 00:26
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt

Bert,

Thanks for your comments. Here is the reasoning behind having the RFC2279 mentioned in the DESCRIPTION
clause of the complience statement for the pktcMtaDevRealmOrgName object.

As per PacketCable requirements, pktcMtaDevRealmOrgName MIB Object should contain OrganizationName
attribute in the X.509 certificate of the Telephony Service Provider. As per RFC3280, the X.509
attributes should be defined as "UTF8String" for all certificates issued after December 31, 2003. Also,
RFC3280 reffers to RFC2279 for the definition of the "UTF8String" type. Further, as per RFC2279, each
"UTF8String" encoded character may contain up to 6 octets, whereas RFC3629 defines up to 4 octests per
each "UTF8String" encoded character. To stay consistant with RFC3280, we also have to define the length
of the pktcMtaDevRealmOrgName MIB Object based on RFC2279 rather than on RFC3629. Hence - the reference
to the obsolete RFC2279 instead of refering to RFC3629 in the DESCRIPTION clause you are rightly pointing to.

To reflect these issues in the MTA MIB, co-authors are proposing the following modifications of the MTA draft:

1. Add the following sub-section to the Section 3 "Introduction" with neccessary additional citations
and explanations:

====================
   3.7 X.509 Certificates Dependencies

As per PacketCable Security Specification [PKT-SP-SEC], EMTA must 
use the authentication mechanism based on the X.509 Public Key 
Infrastructure Certificates as defined in RFC 3280 [RFC3280].

The pktcMtaDevRealmOrgName MIB Object, defined in this document, 
should contain OrganizationName attribute in the X.509 certificate of 
the Telephony Service Provider. As per RFC 3280 [RFC3280], X.509 
attributes are defined as "UTF8String" for all certificates issued
(Continue reading)

Permalink | Reply |
headers
Randy Presuhn | 16 Dec 2005 01:28
Picon

Re: RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt

Hi -

No IS 10646 or Unicode code points have ever been (or ever will be)
assigned that require more than 4 octets to encode in UTF-8.
For details, see section C.2 in
http://www.unicode.org/versions/Unicode4.0.0/appC.pdf

Although the TCs defined in various IETF MIBs can handle any
code point that ever has been or will be defined, ones that are
based on RFC 2279 rather 3629 will permit zillions of invalid code
points.  In my opinion, an implementor would be unwise to use
the RFC 2269 definition rather than the RFC 3629, since it would
permit invalid stuff into his instrumentation,.

For example, despite the RFC 3411 SnmpAdminString TC's reference
to 2269, if I were implementing it today, I'd use the RFC 3629 definition
of UTF-8.  Although the very explicit language in 3411 for SnmpAdminString
says:

|                 Since additional code points are added by
|                 amendments to the 10646 standard from time
|                 to time, implementations must be prepared to
|                 encounter any code point from 0x00000000 to
|                 0x7fffffff.  Byte sequences that do not
|                 correspond to the valid UTF-8 encoding of a
|                 code point or are outside this range are
|                 prohibited.

We should keep in mind that the Unicode and ISO 10646 specifications
have BOTH reduced the upper bound from 7ffffffff to10ffff, and NEVER
(Continue reading)

Permalink | Reply |
headers
Randy Presuhn | 16 Dec 2005 01:51
Picon

Re: RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt

Hi -

Completing my thought...

In  the places where the document currently says things like:
             "The calculation of 
               384 octets comes from the RFC2279 UTF-8 encoding 
               definition whereby the UTF-8 encoded characters 
               are encoded as sequences of 1 to 6 octets." 

We might do something like
             "The calculation of 
               384 octets came from the RFC2279 UTF-8 encoding 
               definition whereby the UTF-8 encoded characters 
               were encoded as sequences of 1 to 6 octets, based on the
               the assumption that code points as high as 0x7ffffffff might
               be used.  Subsequent versions of Unicode and ISO 10646
               have limited the upper bound to 0x10ffff.  Consequently,
               the current version of UTF-8, defined in RFC 3629,
               will never require more than four octets to encode a valid
               code point." 

This would effectively make the RFC 2279 reference informative,
and the RFC 3629 reference normative.

If we wanted to be *really* rigorous, we'd identify a normalization form
as well, but I think that is overkill here, since these aren't used for
indexing.

Randy
(Continue reading)

Permalink | Reply |
headers
Wijnen, Bert (Bert | 14 Dec 2005 14:29
Picon
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt

I still get:

  !! Missing citation for Informative reference:
  P055 L050:    [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO

I see use of RFC2279 inside the MIB module. There is no reference to 2279.
I think you want to replace 2279 with 3629 in the text inside the MIB module
and probably add a citation (outside the MIB module) to RFC3629.

Let us consider that an IETF Last Call comment.

Pls send iesg-secretary <at> ietf.org (and copy me) a reuqest to publis, 
pls do include a PROTO writeup for that.
If you can do so today, we may still be able to get this on Jan 5 telechat

Bert

> -----Original Message-----
> From: Jean-Francois Mule [mailto:jf.mule <at> cablelabs.com]
> Sent: Monday, December 12, 2005 19:06
> To: ipcdn <at> ietf.org; Richard Woundy  <at>  Comcast
> Cc: enechamkin <at> broadcom.com; bwijnen <at> lucent.com
> Subject: RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt 
> 
> 
> Rich and all,
> 
>    Eugene and I submitted a new version of the MTA MIB. It 
> addresses all the comments raised during the IETF 64 meeting 
> in November and some additional feedback received from Bert.
(Continue reading)

Permalink | Reply |
headers
Jean-Francois Mule | 12 Dec 2005 19:05
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt

Rich and all,

   Eugene and I submitted a new version of the MTA MIB. It addresses all the comments raised during the IETF 64
meeting in November and some additional feedback received from Bert.
   See the diff at:
http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/draft-ietf-ipcdn-pktc-mtamib-08-from-07.diff.html

   We would like to request formal publication of this ID.

Eugene and Jean-François 

> -----Original Message-----
> From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org]
> Sent: Friday, December 09, 2005 4:50 PM
> To: i-d-announce <at> ietf.org
> Cc: ipcdn <at> ietf.org
> Subject: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP over Cable Data Network Working
> Group of the IETF.
> 
> 	Title		: Multimedia Terminal Adapter (MTA) Management
>                           Information Base for PacketCable and
>                           IPCablecom compliant devices
> 	Author(s)	: E. Nechamkin, J. Mule
> 	Filename	: draft-ietf-ipcdn-pktc-mtamib-08.txt
> 	Pages		: 61
> 	Date		: 2005-12-9
(Continue reading)

Permalink | Reply |
headers
Woundy, Richard | 22 Feb 2005 17:20
Picon

RE: I-D ACTION:draft-ietf-ipcdn-device-mibv2-07.txt

Folks,

Thanks to a lot of effort by Kevin Marez, we have an update to the
internet-draft that will replace RFC 2669 (Cable Device MIB).

The changes made in this draft are enumerated in this Word document:
<http://www.ipcdn.org/meetings/cdmib-07-changes.doc>.

A marked-up version showing all the changes from version -06 to -07 is
available at
<http://tools.ietf.org/wg/ipcdn/device-mibv2/draft-ietf-ipcdn-device-mibv2-0
7-from-06.diff.html>. Note that this "diff" file is a result of an
experimental service the IETF tools folks are working on.

-- Rich

-----Original Message-----
From: ipcdn-bounces <at> ietf.org [mailto:ipcdn-bounces <at> ietf.org] On Behalf Of
Internet-Drafts <at> ietf.org
Sent: Monday, February 21, 2005 3:48 PM
To: i-d-announce <at> ietf.org
Cc: ipcdn <at> ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-device-mibv2-07.txt

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

	Title		: Cable Device Management Information Base for
DOCSIS
(Continue reading)

Permalink | Reply |
headers
Nakanishi Greg-MGI8179 | 27 Nov 2002 18:04

RE: I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

I believe the -02 version is currently required for cert wave.

greg

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy <at> cable.comcast.com]
> Sent: Wednesday, November 27, 2002 8:48 AM
> To: 'Ian Wheelock'
> Cc: ipcdn <at> ietf.org; DOCSIS OSS (E-mail)
> Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt
> 
> 
> The latest internet-draft version of the Subscriber Management MIB is:
> <http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscrib
> er-mib-07.txt>
> . The recent changes were responses to comments by our IETF 
> MIB doctor.
> 
> This version of the MIB cannot be implemented nor required by 
> a CableLabs
> cert wave, because the root of the MIB is "{ mib-2 xx }", 
> where "xx" is to
> be assigned after IESG approval of the MIB.
> 
> However, the ultimate intent is to require the RFC version of 
> this MIB in a
> future certification wave. If there are problems with this 
> MIB, they should
> be discussed on the ipcdn mailing list.
>
(Continue reading)

Permalink | Reply |
headers
Eduardo Cardona | 29 Nov 2002 05:11
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

Yes, draft 02 is the current one in OSSI spec requirements.
 
Eduardo
-----Original Message-----
From: Nakanishi Greg-MGI8179 [mailto:gnakanishi <at> motorola.com]
Sent: Wed 11/27/2002 3:48 PM
To: 'ipcdn <at> ietf.org'
Cc:
Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

I believe the -02 version is currently required for cert wave.

greg

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy <at> cable.comcast.com]
> Sent: Wednesday, November 27, 2002 8:48 AM
> To: 'Ian Wheelock'
> Cc: ipcdn <at> ietf.org; DOCSIS OSS (E-mail)
> Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt
>
>
> The latest internet-draft version of the Subscriber Management MIB is:
> <http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscrib
> er-mib-07.txt>
> . The recent changes were responses to comments by our IETF
> MIB doctor.
>
> This version of the MIB cannot be implemented nor required by
> a CableLabs
> cert wave, because the root of the MIB is "{ mib-2 xx }",
> where "xx" is to
> be assigned after IESG approval of the MIB.
>
> However, the ultimate intent is to require the RFC version of
> this MIB in a
> future certification wave. If there are problems with this
> MIB, they should
> be discussed on the ipcdn mailing list.
>
> -- Rich
>
> -----Original Message-----
> From: Ian Wheelock [mailto:ianw <at> com21.ie]
> Sent: Wednesday, November 27, 2002 11:00 AM
> To: ipcdn <at> ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt
>
>
> Hi,
>
> is there any decision on whether this version of the mib will
> be required
> for the next certwave ?
>
> there seems to have been extensive changes made to the mib
> compared to -06,
> but i did not see much of this debated on the ipcdn reflector.
>
> is there another reflector/list that discussions have been
> ongoing on ?
>
> thanks
> Ian
>
> _______________________________________________
> IPCDN mailing list
> IPCDN <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/ipcdn
>
_______________________________________________
IPCDN mailing list
IPCDN <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

Permalink | Reply |
headers
Nakanishi Greg-MGI8179 | 27 Nov 2002 23:48

RE: I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

I believe the -02 version is currently required for cert wave.

greg

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy <at> cable.comcast.com]
> Sent: Wednesday, November 27, 2002 8:48 AM
> To: 'Ian Wheelock'
> Cc: ipcdn <at> ietf.org; DOCSIS OSS (E-mail)
> Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt
> 
> 
> The latest internet-draft version of the Subscriber Management MIB is:
> <http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscrib
> er-mib-07.txt>
> . The recent changes were responses to comments by our IETF 
> MIB doctor.
> 
> This version of the MIB cannot be implemented nor required by 
> a CableLabs
> cert wave, because the root of the MIB is "{ mib-2 xx }", 
> where "xx" is to
> be assigned after IESG approval of the MIB.
> 
> However, the ultimate intent is to require the RFC version of 
> this MIB in a
> future certification wave. If there are problems with this 
> MIB, they should
> be discussed on the ipcdn mailing list.
> 
> -- Rich
> 
> -----Original Message-----
> From: Ian Wheelock [mailto:ianw <at> com21.ie]
> Sent: Wednesday, November 27, 2002 11:00 AM
> To: ipcdn <at> ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt
> 
> 
> Hi,
> 
> is there any decision on whether this version of the mib will 
> be required
> for the next certwave ?
> 
> there seems to have been extensive changes made to the mib 
> compared to -06,
> but i did not see much of this debated on the ipcdn reflector.
> 
> is there another reflector/list that discussions have been 
> ongoing on ?
> 
> thanks
> Ian
> 
> _______________________________________________
> IPCDN mailing list
> IPCDN <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/ipcdn
>
Permalink | Reply |
headers
Jean-Francois Mule | 28 Oct 2004 22:33
Favicon

RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-05.txt


The ipcdn mtamib draft 05 addresses all the 'MUST fix' comments received from Dave Thaler, see my email
response from 8/19.

Jean-François 

> -----Original Message-----
> From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org] 
> Sent: Thursday, October 28, 2004 8:58 AM
> To: i-d-announce <at> ietf.org
> Cc: ipcdn <at> ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-05.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories. This draft is a work item of the 
> IP over Cable Data Network Working Group of the IETF.
> 
> 	Title		: Multimedia Terminal Adapter (MTA) 
> Management Information
> 			  Base for PacketCable and IPCablecom 
> compliant devices
> 	Author(s)	: E. Nechamkin, J. Mule
> 	Filename	: draft-ietf-ipcdn-pktc-mtamib-05.txt
> 	Pages		: 51
> 	Date		: 2004-10-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 defines a basic set of managed objects for 
> SNMP- based management of 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-mtam
ib-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> 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-mtamib-05.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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-pktc-mtamib-05.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.
Permalink | Reply |
headers
Woundy, Richard | 27 Nov 2002 17:47
Picon

RE: I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

The latest internet-draft version of the Subscriber Management MIB is:
<http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-07.txt>
. The recent changes were responses to comments by our IETF MIB doctor.

This version of the MIB cannot be implemented nor required by a CableLabs
cert wave, because the root of the MIB is "{ mib-2 xx }", where "xx" is to
be assigned after IESG approval of the MIB.

However, the ultimate intent is to require the RFC version of this MIB in a
future certification wave. If there are problems with this MIB, they should
be discussed on the ipcdn mailing list.

-- Rich

-----Original Message-----
From: Ian Wheelock [mailto:ianw <at> com21.ie]
Sent: Wednesday, November 27, 2002 11:00 AM
To: ipcdn <at> ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-07.txt

Hi,

is there any decision on whether this version of the mib will be required
for the next certwave ?

there seems to have been extensive changes made to the mib compared to -06,
but i did not see much of this debated on the ipcdn reflector.

is there another reflector/list that discussions have been ongoing on ?

thanks
Ian

_______________________________________________
IPCDN mailing list
IPCDN <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn
Permalink | Reply |

Gmane