From ipcdn-bounces@ietf.org Fri Dec 09 11:41:19 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EklJ9-0007jc-O0; Fri, 09 Dec 2005 11:41:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EklJ6-0007hG-1H
	for ipcdn@megatron.ietf.org; Fri, 09 Dec 2005 11:41:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28764;
	Fri, 9 Dec 2005 11:40:16 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EklJD-00021a-0M; Fri, 09 Dec 2005 11:41:24 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.13.4/8.13.4) with ESMTP id jB9Gepkq001994;
	Fri, 9 Dec 2005 09:40:51 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Subject: [ipcdn] Request for publication and proto write-up for
	draft-ietf-ipcdn-device-mibv2-10.txt on the standards track
Date: Fri, 9 Dec 2005 09:40:51 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804011F5AF1@srvxchg.cablelabs.com>
Thread-Topic: [ipcdn] Request for publication and proto write-up for
	draft-ietf-ipcdn-device-mibv2-10.txt on the standards track
Thread-Index: AcXyFaKg9+GIRpw9SgClVrHrploUkQKrzKWA
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, <iesg-secretary@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5596635830a5938fc94538b29441db99
Cc: kevin.marez@motorola.com,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>,
	ipcdn@ietf.org
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="===============1890514300=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1890514300==
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5FCDF.50B450C8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5FCDF.50B450C8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Bert and all,
=20
   This note is the request for publication and proto write-up for=20
draft-ietf-ipcdn-device-mibv2-10.txt.=20
=20
Let us know if you have any questions or concerns with the above by
sending txt to the ipcdn list. Thank you Rich and Kevin for your=20
continued efforts and big thanks to Randy, Bert et al. for the detailed
and constructive MIB doctor and expert reviews.
=20
Jean-Fran=E7ois
jfm@cablelabs.com
IPCDN co-chair.
=20
The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used for the IPCDN Cable Device MIB v2 Internet-Draft.
=20
Here is the proposed PROTO writeup for:
Cable Device Management Information Base for Data-Over-Cable Service
Interface Specification Compliant Cable Modems and Cable Modem
                          Termination Systems
                    draft-ietf-ipcdn-device-mibv2-10
=20
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-10.txt
=20
=20
Requested Publication Status: Proposed Standard
Obsoletes: RFC 2669
PROTO shepherd: Jean-Francois Mule (IPCDN WG co-chair)
------------------------------------------------------------------------
=20
   1.a) Have the chairs personally reviewed this version of the Internet
        Draft (ID), and in particular, do they believe this ID is ready
        to forward to the IESG for publication?
=20
Yes.
One of the 2 IPCDN co-chairs is a co-author and the other is the PROTO
shepherd writing this note. Both have reviewed this version of the ID.
Based on the WG comments, MIB doctors & AD review comments, the ID is
believed to be ready for publication.
=20
=20
   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?
=20
Yes, reviews from both subject-matter experts that are WG members and
MIB doctors who provided valuable comments to improve the quality of
the MIB module.
=20
=20
        Do you have any concerns about the
        depth or breadth of the reviews that have been performed?
=20
No, given the time this ID has been in existence and the number of
revisions due to comments.
=20
=20
   1.c) Do you have concerns that the document needs more review from a
        particular (broader) perspective (e.g., security, operational
        complexity, someone familiar with AAA, etc.)?
=20
No.
=20
   1.d) Do you have any specific concerns/issues with this document that
        you believe the ADs and/or IESG should be aware of?  For
        example, perhaps you are uncomfortable with certain parts of the
        document, or have concerns whether there really is a need for
        it.  In any event, if your issues have been discussed in the WG
        and the WG has indicated it that it still wishes to advance the
        document, detail those concerns in the write-up.
=20
No. The IETF 63 meeting was dedicated to addressing all the remaining
WG comments and the draft update does close those open issues. No other
concerns from the PROTO shepherd.
=20
   1.e) How solid is the WG consensus behind this document? Does it
        represent the strong concurrence of a few individuals, with
        others being silent, or does the WG as a whole understand and
        agree with it?
=20
This document represents the WG consensus as a whole: the WG as a whole
understands and agrees with it.
=20
   1.f) Has anyone threatened an appeal or otherwise indicated extreme
        discontent?  If so, please summarise the areas of conflict in
        separate email to the Responsible Area Director.
=20
No. An explicit request for intent to appeal was made on the list on
November 25, 2005.
=20
   1.g) Have the chairs verified that the document adheres to all of the
        ID nits? (see http://www.ietf.org/ID-Checklist.html) =
<http://www.ietf.org/ID-Checklist.html%29> .
=20
The ID nits checker (v1.82) was ran on Nov 25 2005 and found no issues.
idnits 1.82 output:
-----------
tmp/draft-ietf-ipcdn-device-mibv2-10.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.
    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
    No nits found.
---------------
=20
=20
   1.h) Is the document split into normative and informative references?
=20
Yes.
=20
        Are there normative references to IDs, where the IDs are not
        also ready for advancement or are otherwise in an unclear state?
        (note here that the RFC editor will not publish an RFC with
        normative references to IDs, it will delay publication until all
        such IDs are also ready for publication as RFCs.)
=20
No.
=20
   1.i) For Standards Track and BCP documents, the IESG approval
        announcement includes a write-up section with the following
        sections:
=20
        *    Technical Summary
=20
        *    Working Group Summary
=20
        *    Protocol Quality
Ok.
=20
   1.j) Please provide such a write-up.  Recent examples can be found in
        the "protocol action" announcements for approved documents.
=20
--- Technical Summary
=20
   This document is a revision of the standards track RFC 2669.
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines a basic set of managed objects for SNMP-
   based management of DOCSIS-compliant Cable Modems and Cable Modem
   Termination Systems.
=20
=20
--- Working Group Summary
=20
   The Working Group has consensus to publish this document as a
   Proposed Standard.
=20
=20
--- Protocol Quality
=20
   The MIB module has been reviewed by Randy Presuhn. The overall =
quality
   with respect to DOCSIS functionality has been reviewed by Greg White
   and Eduardo Cardona. This document has been reviewed for the IESG by
   Bert Wijnen.
=20

=20

=20

> -----Original Message-----

> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]

> Sent: Friday, November 25, 2005 4:12 PM

> To: Jean-Francois Mule; Richard Woundy @ Comcast; ipcdn@ietf.org

> Subject: RE: Advancing draft-ietf-ipcdn-device-mibv2-10.txt on the

> standards track

>=20

> I did a last check of the document.

>=20

> - In the DESCRIPTION clause of the MODULE-IDENTITY you state:

>                 Copyright (C) The Internet Society (2005). The initial

>                 version of this MIB module was published in RFC XXXX;

>                 for full legal notices see the RFC itself.

>                 Supplementary information may be available at:

>                 http://www.ietf.org/copyrights/ianamib.html."

>   Those last two lines can go away. This is not an IANA maintained

>   MIB module, so their copyrights have nothing to do with this.

>=20

> You can consider that as an early IETF Last Call comment, and we can

> fix it with a note to RFC-Editor if this is all that gets reported.

>=20

> So I am ready for IETF Last Call as soon as I get the PROTO report,

> which comes with a "request to publish as Proposed Standard" (and

> plx send to iesg-secretary@ietf.org and copy me).

>=20

> Bert


------_=_NextPart_001_01C5FCDF.50B450C8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-compose;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 89.95pt 1.0in 89.95pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1><pre><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>Bert and =
all,<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; This note is the request for =
publication and proto write-up for =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>draft-ietf-ipcdn-device-mibv2-10.txt. =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Let us =
know if you have any questions or concerns with the above =
by<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>sending =
txt to the ipcdn list. Thank you Rich and Kevin for your =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>continued =
efforts and big thanks to Randy, Bert et al. for the =
detailed<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>and =
constructive MIB doctor and expert =
reviews.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Jean-Fran&ccedil;ois<o:p></o:p></span></font><=
/pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>jfm@cablelabs.com<o:p></o:p></span></font></pr=
e><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>IPCDN =
co-chair.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>The PROTO =
process (cf. =
draft-ietf-proto-wgchair-doc-shepherding-05.txt)<o:p></o:p></span></font>=
</pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>is being =
used for the IPCDN Cable Device MIB v2 =
Internet-Draft.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Here is =
the proposed PROTO writeup for:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Cable =
Device Management Information Base for Data-Over-Cable =
Service<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Interface =
Specification Compliant Cable Modems and Cable =
Modem<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;Termination =
Systems<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ietf-ipcdn-device-mibv2-10<o:p></o:p></span></font></pre><pre><font=

size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>ftp://ftp.ietf.org/internet-drafts/draft-ietf-=
ipcdn-device-mibv2-10.txt<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Requested =
Publication Status: Proposed =
Standard<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Obsoletes: RFC =
2669<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>PROTO =
shepherd: <st1:PersonName
w:st=3D"on">Jean-Francois Mule</st1:PersonName> (IPCDN WG =
co-chair)<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dslateblue face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:slateblue'>--------------------------------------------------------=
----------------</span></font><o:p></o:p></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.a) Have the chairs personally =
reviewed this version of the =
Internet<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Draft (ID), and in particular, do they believe this ID is =
ready<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
forward to the IESG for =
publication?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Yes.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>One of =
the 2 IPCDN co-chairs is a co-author and the other is the =
PROTO<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>shepherd =
writing this note. Both have reviewed this version of the =
ID.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Based on =
the WG comments, MIB doctors &amp; AD review comments, the ID =
is<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>believed =
to be ready for publication.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.b) Has the document had =
adequate review from both key WG =
members<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and key non-WG members?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Yes, =
reviews from both subject-matter experts that are WG members =
and<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>MIB =
doctors who provided valuable comments to improve the quality =
of<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>the MIB =
module.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do =
you have any concerns about the<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
depth or breadth of the reviews that have been =
performed?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>No, given =
the time this ID has been in existence and the number =
of<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>revisions =
due to comments.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.c) Do you have concerns that =
the document needs more review from =
a<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular (broader) perspective (e.g., security, =
operational<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
complexity, someone familiar with AAA, =
etc.)?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>No.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.d) Do you have any specific =
concerns/issues with this document =
that<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
you believe the ADs and/or IESG should be aware of?&nbsp; =
For<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
example, perhaps you are uncomfortable with certain parts of =
the<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
document, or have concerns whether there really is a need =
for<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
it.&nbsp; In any event, if your issues have been discussed in the =
WG<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and the WG has indicated it that it still wishes to advance =
the<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
document, detail those concerns in the =
write-up.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>No. The =
IETF 63 meeting was dedicated to addressing all the =
remaining<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>WG =
comments and the draft update does close those open issues. No =
other<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>concerns =
from the PROTO shepherd.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.e) How solid is the WG =
consensus behind this document? Does =
it<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
represent the strong concurrence of a few individuals, =
with<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
others being silent, or does the WG as a whole understand =
and<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
agree with it?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This =
document represents the WG consensus as a whole: the WG as a =
whole<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>understands and agrees with =
it.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.f) Has anyone threatened an =
appeal or otherwise indicated =
extreme<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
discontent?&nbsp; If so, please summarise the areas of conflict =
in<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
separate email to the Responsible Area =
Director.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>No. An =
explicit request for intent to appeal was made on the list =
on<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>November =
25, 2005.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.g) Have the chairs verified =
that the document adheres to all of =
the<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ID =
nits? (see <a
href=3D"http://www.ietf.org/ID-Checklist.html%29">http://www.ietf.org/ID-=
Checklist.html)</a>.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>The ID =
nits checker (v1.82) was ran on Nov 25 2005 and found no =
issues.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>idnits =
1.82 output:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dslateblue face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:slateblue'>-----------</span></font><o:p></o:p></pre><pre><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>tmp/draft-ietf-ipcdn-device-mibv2-10.txt:<o:p>=
</o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&nbsp; =
Checking nits according to <a
href=3D"http://www.ietf.org/ID-Checklist.html">http://www.ietf.org/ID-Che=
cklist.html</a>:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; Checking conformance with =
RFC 3978/3979 boilerplate...<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; the boilerplate looks =
good.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; No nits =
found.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&nbsp; =
Checking nits according to <a
href=3D"http://www.ietf.org/ietf/1id-guidelines.txt">http://www.ietf.org/=
ietf/1id-guidelines.txt</a>:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; Nothing found here (but =
these checks do not cover all =
of<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; 1id-guidelines.txt =
yet).<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&nbsp; =
Miscellaneous warnings:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; =
None.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; No nits =
found.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dslateblue face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:slateblue'>---------------</span></font><o:p></o:p></pre><pre><font=

size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.h) Is the document split into =
normative and informative =
references?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Yes.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Are there normative references to IDs, where the IDs are =
not<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
also ready for advancement or are otherwise in an unclear =
state?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(note here that the RFC editor will not publish an RFC =
with<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
normative references to IDs, it will delay publication until =
all<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
such IDs are also ready for publication as =
RFCs.)<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>No.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.i) For Standards Track and BCP =
documents, the IESG approval<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
announcement includes a write-up section with the =
following<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sections:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp;&nbsp;&nbsp; Technical =
Summary<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp; Working Group =
Summary<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp;&nbsp;&nbsp; Protocol =
Quality<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Ok.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; 1.j) Please provide such a =
write-up.&nbsp; Recent examples can be found =
in<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the &quot;protocol action&quot; announcements for approved =
documents.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><b><=
font
size=3D2 color=3Dseagreen face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:seagreen;font-weight:bold'>--- Technical =
Summary</span></font></b><o:p></o:p></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; This document is a revision of =
the standards track RFC 2669.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; This memo defines a portion of =
the Management Information Base =
(MIB)<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; for use with network management =
protocols in the Internet =
community.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; In particular, it defines a =
basic set of managed objects for =
SNMP-<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; based management of =
DOCSIS-compliant Cable Modems and Cable =
Modem<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Termination =
Systems.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><b><=
font
size=3D2 color=3Dseagreen face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:seagreen;font-weight:bold'>--- Working Group =
Summary</span></font></b><o:p></o:p></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The Working Group has consensus =
to publish this document as a<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Proposed =
Standard.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><b><=
font
size=3D2 color=3Dseagreen face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:seagreen;font-weight:bold'>--- Protocol =
Quality</span></font></b><o:p></o:p></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; The MIB module has been reviewed =
by <st1:PersonName
w:st=3D"on">Randy Presuhn</st1:PersonName>. The overall =
quality<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; with respect to DOCSIS =
functionality has been reviewed by <st1:PersonName
w:st=3D"on">Greg =
White</st1:PersonName><o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; and <st1:PersonName
w:st=3D"on">Eduardo Cardona</st1:PersonName>. This document has been =
reviewed for the IESG by<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; Bert =
Wijnen.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; -----Original Message-----</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; From: Wijnen, Bert (Bert) =
[mailto:bwijnen@lucent.com]</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Sent: Friday, November 25, 2005 4:12 =
PM</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; To: <st1:PersonName w:st=3D"on">Jean-Francois =
Mule</st1:PersonName>;
Richard Woundy @ Comcast; ipcdn@ietf.org</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Subject: RE: Advancing draft-ietf-ipcdn-device-mibv2-10.txt =
on the</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; standards track</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; I did a last check of the =
document.</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; - In the DESCRIPTION clause of the MODULE-IDENTITY you =
state:</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Copyright (C) The Internet Society (2005). The =
initial</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
version of this MIB module was published in RFC =
XXXX;</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
for full legal notices see the RFC itself.</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Supplementary information may be available =
at:</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http://www.ietf.org/copyrights/ianamib.html.&quot;</span><o:p></o:p></fon=
t></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp; Those last two lines can go away. This is not =
an IANA
maintained</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp; MIB module, so their copyrights have nothing to =
do
with this.</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; You can consider that as an early IETF Last Call comment, =
and we
can</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; fix it with a note to RFC-Editor if this is all that gets
reported.</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; So I am ready for IETF Last Call as soon as I get the PROTO
report,</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; which comes with a &quot;request to publish as Proposed
Standard&quot; (and</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; plx send to iesg-secretary@ietf.org and copy =
me).</span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span><o:p></o:p></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Bert</span><o:p></o:p></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C5FCDF.50B450C8--


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

--===============1890514300==--




From ipcdn-bounces@ietf.org Fri Dec 09 18:50:46 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eks0k-0004Ed-Nh; Fri, 09 Dec 2005 18:50:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eks06-0003mz-Ks; Fri, 09 Dec 2005 18:50:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29310;
	Fri, 9 Dec 2005 18:49:10 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Eks0K-0003uC-Hx; Fri, 09 Dec 2005 18:50:21 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1Eks02-00086d-4x; Fri, 09 Dec 2005 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Eks02-00086d-4x@newodin.ietf.org>
Date: Fri, 09 Dec 2005 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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>
Sender: ipcdn-bounces@ietf.org
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		: 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
	
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-mtamib-08.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-mtamib-08.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-mtamib-08.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: <2005-12-9163509.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipcdn-pktc-mtamib-08.txt

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

Content-Type: text/plain
Content-ID: <2005-12-9163509.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 Dec 12 13:06:23 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Els47-0002RL-Nw; Mon, 12 Dec 2005 13:06:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Els3u-0002Q6-DD
	for ipcdn@megatron.ietf.org; Mon, 12 Dec 2005 13:06:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24774
	for <ipcdn@ietf.org>; Mon, 12 Dec 2005 13:05:12 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Els4i-0005VG-La
	for ipcdn@ietf.org; Mon, 12 Dec 2005 13:07:01 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.13.4/8.13.4) with ESMTP id jBCI5glY018671;
	Mon, 12 Dec 2005 11:05:47 -0700 (MST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Dec 2005 11:05:42 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804011F5BE7@srvxchg.cablelabs.com>
Thread-Topic: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt 
Thread-Index: AcX9IJHOkOKCG9BoS2+cwrCnfdp4rgCJacJw
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <ipcdn@ietf.org>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: bwijnen@lucent.com, enechamkin@broadcom.com
Subject: [ipcdn] RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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-ip=
cdn-pktc-mtamib-08-from-07.diff.html

   We would like to request formal publication of this ID.

Eugene and Jean-Fran=E7ois=20

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Friday, December 09, 2005 4:50 PM
> To: i-d-announce@ietf.org
> Cc: ipcdn@ietf.org
> Subject: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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		: 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
>=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 defines a basic set of managed objects for
>    SNMP-based management of PacketCable and IPCablecom compliant
>    Multimedia Terminal Adapter devices.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-
> 08.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-mtamib-08.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-mtamib-08.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 Tue Dec 13 18:12:55 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmJKJ-0003IT-IP; Tue, 13 Dec 2005 18:12:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmJKG-0003HF-BO
	for ipcdn@megatron.ietf.org; Tue, 13 Dec 2005 18:12:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12736
	for <ipcdn@ietf.org>; Tue, 13 Dec 2005 18:11:49 -0500 (EST)
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmJLF-0006ra-Ij
	for ipcdn@ietf.org; Tue, 13 Dec 2005 18:13:54 -0500
Received: from ([10.20.9.174])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.15560496;
	Tue, 13 Dec 2005 18:12:10 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.211); Tue, 13 Dec 2005 18:11:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 13 Dec 2005 18:11:18 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73016B15F2@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: IETF64 - IPCDN meeting minutes (preliminary)
Thread-Index: AcX0IYUMDQC+Gtu1TVGpbyyvSJBq3QMF86MA
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>
X-OriginalArrivalTime: 13 Dec 2005 23:11:18.0666 (UTC)
	FILETIME=[86398EA0:01C6003A]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0a1b1a6d35de6f81974769730a8306bf
Cc: Jean-Francois Mule <jf.mule@CableLabs.com>,
	"Ipcdn \(E-mail\)" <ipcdn@ietf.org>
Subject: [ipcdn] RE: IETF64 - IPCDN meeting minutes (preliminary)
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="===============2059425066=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2059425066==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6003A.85DA07DE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6003A.85DA07DE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, Bert. I believe I incorporated all of these suggestions to the
final posted minutes:
=20
http://www3.ietf.org/proceedings/05nov/minutes/ipcdn.html
=20
-- Rich

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
Sent: Monday, November 28, 2005 8:41 AM
To: Woundy, Richard; Ipcdn (E-mail)
Cc: Wijnen, Bert (Bert); Jean-Francois Mule
Subject: RE: IETF64 - IPCDN meeting minutes (preliminary)


Inline

-----Original Message-----
From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
Sent: Tuesday, November 22, 2005 02:46
To: Ipcdn (E-mail)
Cc: Wijnen, Bert (Bert); Jean-Francois Mule; Woundy, Richard
Subject: IETF64 - IPCDN meeting minutes (preliminary)


Folks,
=20
Below is my working copy of the meeting minutes from our WG session in
Vancouver.
=20
Please send corrections to the mailing list and to myself -- especially
concerning the WG recommendations and next steps.
=20
Thanks.
=20
-- Rich
=20
IETF IPCDN Meeting
Vancouver, British Columbia
Thursday November 10, 2005

Reported by Richard Woundy (richard_woundy@cable.comcast.com)=20


WG Meeting Summary and Administration


The IPCDN WG met to discuss the progress of various MIB documents,
especially the outstanding PacketCable/IPCablecom and DOCSIS
internet-drafts.=20

The DOCSIS BPI+ MIB was published as RFC 4131 in September. The DOCSIS
QoS MIB and the DOCSIS Event Notification Management MIB are on the RFC
Editor Queue.=20

Most of the meeting discussion centered on resolving open issues with
the PacketCable/IPCablecom MTA MIB (syntax of Kerberos realm names and
realm organization names, and a textual convention for encryption
algorithms), and with the PacketCable/IPCablecom Management Event MIB
(whether event throttling applies to local logging on the cable modem).
The PacketCable/IPCableCom NCS Signaling MIB, DOCSIS Cable Device MIB,
and DOCSIS RFIv2 MIB were also discussed, with a focus on the next steps
to get to the 'Publication Requested' state for all five
internet-drafts.=20

There is a strong desire by the WG to conclude all DOCSIS and
PacketCable/IPCablecom MIB drafts by December 2005. =20

=20

Aggressive! But let's go for it, we have 3 more days!

Maybe you meant end-of-december 2005. With all the holidays, that will
arrive soon too!

 There were about ten attendees at the WG session in Vancouver. Total
meeting time was one hour.=20


PacketCable/IPCableCom MTA MIB


Eugene Nechamkin and Jean-Francois Mule produced version 07 of the MTA
MIB draft, to address comments from the AD review (Bert Wijnen) and from
the IPCDN mailing list. The resolution of these comments were posted
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01806.html>  on
the mailing list. Most comments were resolved with simple editorial
fixes. One significant addition is specification of the same encryption
algorithms as the BPI+ MIB (RFC 4131, ref: DocsBpkmDataEncryptAlg).=20

The WG discussion was centered on the proper MIB object SYNTAX for
Kerberos realm names and Kerberos realm organization names.=20

With respect to the Kerberos realm organization name
(pktcMtaDevRealmOrgName), X.509 and RFC 2459 contrain the length of the
organization name to 64 characters. The characters may be encoded as a
UTF8String, so each character may occupy between one and six octets.
Therefore, a single organization name may occupy up to 384 octets. The
current MIB object has a SYNTAX of SnmpAdminString(SIZE (1..255)).=20

The WG recommends to change the pktcMtaDevRealmOrgName object as
follows:=20


1.	Remove the sentence referring to the "o=3D" prefix in the
DESCRIPTION clause. Do not include the "o=3D" prefix in the value of =
this
MIB object.=20

2.	Change the SYNTAX of this object to LongUtf8String, imported
from the SYSAPPL-MIB defined in RFC 2287. This enables a maximum size of
1024 octets (for future growth).=20

3.	Add a compliance statement for this object to limit the maximum
size of the object to 384 octets, and include justification, e.g. each
UTF-8 character can be up to 6 octets long, and the organization name
may contain up to 64 UTF-8 characters.=20



Three distinct MIB objects contain a Kerberos realm name:
pktcMtaDevProvKerbRealmName, pktcMtaDevRealmName, and
pktcMtaDevCmsKerbRealmName. RFC 4120 specifies a syntax of GeneralString
for the Kerberos realm name, although the RFC says the realm name may be
non-ASCII (UTF8String) in the future. The WG recommendation is to
continue to use SnmpAdminString as the SYNTAX for these three MIB
objects.=20

This draft also has a new textual convention for MTA configuration file
encryption algorithms, PktcMtaDevProvEncryptAlg. This textual convention
enables future support of triple-DES and AES encryption, similar to the
DocsBpkmDataEncryptAlg textual convention in the DOCSIS BPI+ MIB (RFC
4131). It was suggested to compare the PktcMtaDevProvEncryptAlg and
DocsBpkmDataEncryptAlg textual conventions, and if they were identical,
then have the MTA MIB IMPORT DocsBpkmDataEncryptAlg from the BPI+ MIB.=20

Editor's note: the DocsBpkmDataEncryptAlg includes 40-bit and 56-bit DES
encryption but not 64-bit DES encryption as in PktcMtaDevProvEncryptAlg.
These textual conventions are NOT identical nor compatible.=20

The next steps for this internet-draft are:=20


1.	Bert Wijnen will respond to the author's email
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01806.html>  and
confirm whether or not the draft addresses the AD review comments.=20

2.	The authors will incorporate the recommended changes to the
pktcMtaDevRealmOrgName MIB object.=20

3.	Bert Wijnen will put the draft into the 'Publication Requested'
state.  =20

4.=09

I probably have said that "I could put it in Publication Requested".
But I want/need a PROTO writeup as well.
So as per my email of past weekend, pls do the proto writeup and send a
request (from one of
the WG chairs) to the iesg-secretary@ietf.org and ask for publication as
Proposed Standard.
Pls do copy me. =20
And pls do only do so, after revision 8 has been posted, because that is
(as per our email exchange
over the weekend) the one that you want published. Current ID_tracker
state of this doc is "Revised ID needed"
which will change when new revision shows up.




PacketCable/IPCableCom NCS Signaling MIB=20


I'd add that this is document:  draft-ietf-ipcdn-pktc-signaling-09.txt


 Gordon Beacham, Satish Kumar, and Sumanth Channabasappa submitted
version 09 of the NCS Signaling MIB draft, to address comments from the
MIB doctor and various WG participants. The resolution of these comments
were posted
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01809.html>  on
the mailing list.=20


Significant updates included changes to a number of MIB objects in the
pktcSigDevMultiFreqToneTable, and the removal of the
pktcNcsEndPntConfigTxGain and pktcNcsEndPntConfigRxGain objects.=20

There were no comments concerning this internet-draft in this meeting.=20

The next steps for this internet-draft are:=20


1.	The WG co-chairs will review this draft.=20

2.	The co-chairs will request to put the draft into the
'Publication Requested' state. (Editor's note: does this imply a PROTO
writeup for this draft?) =20

Yes, for every "publication requested as XX" (where XX is Proposed
Standard, or the state you want)  I want/need a PROTO
writeup.
=20
This doc is in a weird "expired/dead" state in the ID-tracker. I am
following up on that with secretariat to get that
fixed. Pls keep your work going to get PROTO writeup done and to send
request to publish.
=20




PacketCable/IPCableCom Management Event MIB=20


=20


I'dd add that this is document: draft-ietf-ipcdn-pktc-eventmess-05.txt
<http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-05.
txt>=20


=20


also this doc is in a weird DEAD state in ID-tracker.


I am following up with secretrariat to get that fixed.


=20


Wim De Ketelaere, Eugene Nechamkin, and Sumanth Channabasappa submitted
version 05 of the PacketCable/IPCableCom Management Event MIB draft,
responding to comments from a review by Greg Nakanishi and additional
feedback from Randy Presuhn. The resolution of these comments were
posted
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01810.html>  on
the mailing list.=20

There was some discussion in the meeting about whether the event
throttling objects (pktcDevEvThrottleAdminStatus,
pktcDevEvThrottleThreshold, and pktcDevEvThrottleInterval) apply to
local logging of events, or only to network transmissions of events via
SNMP or SYSLOG messages. The current throttling MIB objects only refer
to SNMP and SYSLOG, but pktcDevEventDescrReporting and pktcDevEvLogType
refer to local logging.=20

The WG recommends to add the following text to the DESCRIPTION of
pktcDevEvThrottleAdminStatus: "The impact of event throttling controls
on local logging is an implementation-specific matter."=20

Editor's note: The following DESCRIPTION of pktcDevEvLogType suggests
that the throttling controls do NOT apply to local logging. If
throttling of local logging is implementation-specific, then at least
this DESCRIPTION should be revised.=20

<FONT face=3D"Times New Roman" size=3D3>   pktcDevEvLogType OBJECT-TYPE=20

       SYNTAX      BITS {=20

                   local(0),=20

                   syslog (1),=20

                   trap (2),=20

                   inform (3)=20

                   }=20

       MAX-ACCESS  read-only=20

       STATUS      current=20

       DESCRIPTION=20

               "This MIB Object contains the kind of actions taken by =20

                the MTA when the event under consideration occurred.=20

   =20

                A bit with a value of 1 indicates the corresponding=20

                action was taken. Setting it to a value of 0 indicates =20

                that the corresponding action was not taken.=20

    =20

                An event may trigger one or more actions (e.g.: Syslog =20

                and SNMP) or may remain as a local event since =20

                transmissions could be disabled or inhibited as defined


                by the Throttle MIB Objects."=20

                =20

       ::=3D { pktcDevEventLogEntry 7 }=20

</FONT>
=20
As I think I stated at the meeting.
Pls be very explicit in the text of the DESCRIPTION clause(s) as to what

people can expect.=20
<FONT face=3DArial color=3D#0000ff></FONT>




  The next steps for this internet-draft are:=20


1.	The WG co-chairs will review this draft.=20

2.	The co-chairs will request to put the draft into the
'Publication Requested' state. (Editor's note: does this imply a PROTO
writeup for this draft?)  =20

3.=09

Yes=20




DOCSIS Cable Device MIB (replacing RFC2669)=20


=20


I would add: this is document: draft-ietf-ipcdn-device-mibv2-10.txt
<http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-10.tx
t> =20


Kevin Marez and Richard Woundy produced version 10 of the DOCSIS Cable
Device MIB draft, to address comments from the AD review (Bert Wijnen)
and from the MIB doctor review. The resolution of the AD review comments
were posted
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html>  on
the mailing list. Most comments were resolved with simple editorial
fixes.=20

Two significant changes in version 10 discussed in the meeting were the
new narrative text for MIB module IMPORTs and REFERENCE clauses (section
3.1.1), and the new narrative text discussing the persistance model for
cable modem MIB objects (section 3.1.2). There were no significant
comments on the IMPORT/REFERENCE narrative text, although this is
different from the approach taken by other IPCDN internet-drafts. Bert
noted that there was no MUST statements in the persistance model
narrative, but that was OK since the normative persistance requirements
were in the MIB object definitions.=20

The next step for this internet-draft is for the IPCDN co-chairs (in
this particular case, Jean-Francois Mule) to write a "Protocol Write-Up"
to prepare for the IESG review process. =20

=20

Yep, the so called PROTO write up.

And that normally comes in with a "request t  to publish as XX" (XX is
the stds track you want, i believe PS for this doc).

Pls send to iesg-secretary@ietf.org and cc: myself.

=20


DOCSIS RFIv2 MIB (replacing RFC2670)=20


This is document: draft-ietf-ipcdn-docs-rfmibv2-14.txt
<http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.tx
t> =20


Eduardo Cardona produced version 14 of the DOCSIS RFIv2 MIB, in response
to comments from the AD
<http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01694.html>
review (Bert Wijnen).=20

There were no comments concerning this internet-draft in this meeting.=20

The next steps for this internet-draft are:=20


1.	The WG co-chairs will review this draft.=20

2.	The co-chairs will request to put the draft into the
'Publication Requested' state. (Editor's note: does this imply a PROTO
writeup for this draft?)  =20

3.=09

Yep, see above
=20
Bert=20




IPCDN Next Steps


The co-chairs will review plans for promoting, finalizing, and reviewing
current IPCDN MIBs, with a focus on the DOCSIS and
PacketCable/IPCableCom MIB internet-drafts.=20


Co-chairs:


Richard Woundy <Richard_Woundy@cable.comcast.com>
Jean-Francois Mule' <jf.mule@cablelabs.com>=20


------_=_NextPart_001_01C6003A.85DA07DE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D242440223-13122005>Thanks, Bert. I believe I incorporated all of =
these=20
suggestions to the final posted minutes:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D242440223-13122005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D242440223-13122005><A=20
href=3D"http://www3.ietf.org/proceedings/05nov/minutes/ipcdn.html">http:/=
/www3.ietf.org/proceedings/05nov/minutes/ipcdn.html</A></SPAN></FONT></DI=
V>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D242440223-13122005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D242440223-13122005>--=20
Rich</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Wijnen, Bert=20
  (Bert) [mailto:bwijnen@lucent.com] <BR><B>Sent:</B> Monday, November =
28, 2005=20
  8:41 AM<BR><B>To:</B> Woundy, Richard; Ipcdn (E-mail)<BR><B>Cc:</B> =
Wijnen,=20
  Bert (Bert); Jean-Francois Mule<BR><B>Subject:</B> RE: IETF64 - IPCDN =
meeting=20
  minutes (preliminary)<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D422445911-28112005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Inline</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Woundy, Richard=20
    [mailto:Richard_Woundy@cable.comcast.com]<BR><B>Sent:</B> Tuesday, =
November=20
    22, 2005 02:46<BR><B>To:</B> Ipcdn (E-mail)<BR><B>Cc:</B> Wijnen, =
Bert=20
    (Bert); Jean-Francois Mule; Woundy, Richard<BR><B>Subject:</B> =
IETF64 -=20
    IPCDN meeting minutes (preliminary)<BR><BR></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005>Folks,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D508554001-22112005>Below is my=20
    working copy of the meeting minutes from our WG session in=20
    Vancouver.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D508554001-22112005>Please send=20
    corrections to the mailing list and to myself -- =
especially&nbsp;concerning=20
    the WG recommendations and next steps.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005>Thanks.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN class=3D508554001-22112005>-- =

    Rich</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D508554001-22112005></SPAN></FONT>&nbsp;</DIV><FONT =
face=3DArial=20
    size=3D2><SPAN class=3D508554001-22112005>
    <P><B>IETF IPCDN Meeting</B><BR><B>Vancouver, British=20
    Columbia</B><BR><B>Thursday November 10, 2005</B><BR><BR>Reported by =
Richard=20
    Woundy (richard_woundy@cable.comcast.com) </P>
    <H4><A name=3Dsummary>WG Meeting Summary and Administration</A></H4>
    <P>The IPCDN WG met to discuss the progress of various MIB =
documents,=20
    especially the outstanding PacketCable/IPCablecom and DOCSIS=20
    internet-drafts. </P>
    <P>The DOCSIS BPI+ MIB was published as RFC 4131 in September. The =
DOCSIS=20
    QoS MIB and the DOCSIS Event Notification Management MIB are on the =
RFC=20
    Editor Queue. </P>
    <P>Most of the meeting discussion centered on resolving open issues =
with the=20
    PacketCable/IPCablecom MTA MIB (syntax of Kerberos realm names and =
realm=20
    organization names, and a textual convention for encryption =
algorithms), and=20
    with the PacketCable/IPCablecom Management Event MIB (whether event=20
    throttling applies to local logging on the cable modem). The=20
    PacketCable/IPCableCom NCS Signaling MIB, DOCSIS Cable Device MIB, =
and=20
    DOCSIS RFIv2 MIB were also discussed, with a focus on the next steps =
to get=20
    to the 'Publication Requested' state for all five internet-drafts. =
</P>
    <P>There is a strong desire by the WG to conclude all DOCSIS and=20
    PacketCable/IPCablecom MIB drafts by December 2005.&nbsp;<SPAN=20
    class=3D422445911-28112005><FONT =
color=3D#0000ff>&nbsp;</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</P>
    <P><SPAN class=3D422445911-28112005><FONT =
color=3D#0000ff>Aggressive! But let's=20
    go for it, we have 3 more days!</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>Maybe you =
meant=20
    end-of-december 2005. With all the holidays, that will arrive soon=20
    too!</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005>&nbsp;</SPAN>There were about =
ten=20
    attendees at the WG session in Vancouver. Total meeting time was one =
hour.=20
    </P>
    <H4><A name=3Dmtamib>PacketCable/IPCableCom MTA MIB</A></H4>
    <P>Eugene Nechamkin and Jean-Francois Mule produced version 07 of =
the MTA=20
    MIB draft, to address comments from the AD review (Bert Wijnen) and =
from the=20
    IPCDN mailing list. The resolution of these comments were <A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01806.html=
">posted</A>=20
    on the mailing list. Most comments were resolved with simple =
editorial=20
    fixes. One significant addition is specification of the same =
encryption=20
    algorithms as the BPI+ MIB (RFC 4131, ref: DocsBpkmDataEncryptAlg). =
</P>
    <P>The WG discussion was centered on the proper MIB object SYNTAX =
for=20
    Kerberos realm names and Kerberos realm organization names. </P>
    <P>With respect to the Kerberos realm organization name=20
    (pktcMtaDevRealmOrgName), X.509 and RFC 2459 contrain the length of =
the=20
    organization name to 64 characters. The characters may be encoded as =
a=20
    UTF8String, so each character may occupy between one and six octets. =

    Therefore, a single organization name may occupy up to 384 octets. =
The=20
    current MIB object has a SYNTAX of SnmpAdminString(SIZE (1..255)). =
</P>
    <P>The WG recommends to change the pktcMtaDevRealmOrgName object as =
follows:=20

    <OL>
      <LI>Remove the sentence referring to the "o=3D" prefix in the =
DESCRIPTION=20
      clause. Do not include the "o=3D" prefix in the value of this MIB =
object.=20
      <LI>Change the SYNTAX of this object to LongUtf8String, imported =
from the=20
      SYSAPPL-MIB defined in RFC 2287. This enables a maximum size of =
1024=20
      octets (for future growth).=20
      <LI>Add a compliance statement for this object to limit the =
maximum size=20
      of the object to 384 octets, and include justification, e.g. each =
UTF-8=20
      character can be up to 6 octets long, and the organization name =
may=20
      contain up to 64 UTF-8 characters. </LI></OL>
    <P></P>
    <P>Three distinct MIB objects contain a Kerberos realm name:=20
    pktcMtaDevProvKerbRealmName, pktcMtaDevRealmName, and=20
    pktcMtaDevCmsKerbRealmName. RFC 4120 specifies a syntax of =
GeneralString for=20
    the Kerberos realm name, although the RFC says the realm name may be =

    non-ASCII (UTF8String) in the future. The WG recommendation is to =
continue=20
    to use SnmpAdminString as the SYNTAX for these three MIB objects. =
</P>
    <P>This draft also has a new textual convention for MTA =
configuration file=20
    encryption algorithms, PktcMtaDevProvEncryptAlg. This textual =
convention=20
    enables future support of triple-DES and AES encryption, similar to =
the=20
    DocsBpkmDataEncryptAlg textual convention in the DOCSIS BPI+ MIB =
(RFC 4131).=20
    It was suggested to compare the PktcMtaDevProvEncryptAlg and=20
    DocsBpkmDataEncryptAlg textual conventions, and if they were =
identical, then=20
    have the MTA MIB IMPORT DocsBpkmDataEncryptAlg from the BPI+ MIB. =
</P>
    <P>Editor's note: the DocsBpkmDataEncryptAlg includes 40-bit and =
56-bit DES=20
    encryption but not 64-bit DES encryption as in =
PktcMtaDevProvEncryptAlg.=20
    These textual conventions are NOT identical nor compatible. </P>
    <P>The next steps for this internet-draft are:=20
    <OL>
      <LI>Bert Wijnen will respond to the author's <A=20
      =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01806.html=
">email</A>=20
      and confirm whether or not the draft addresses the AD review =
comments.=20
      <LI>The authors will incorporate the recommended changes to the=20
      pktcMtaDevRealmOrgName MIB object.=20
      <LI>Bert Wijnen will put the draft into the 'Publication =
Requested'=20
      state.&nbsp;<SPAN class=3D422445911-28112005><FONT=20
      color=3D#0000ff>&nbsp;</FONT></SPAN>=20
      <LI><SPAN class=3D422445911-28112005></SPAN></LI></OL>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>I =
probably have said=20
    that "I could&nbsp;put it in Publication =
Requested".</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>But I =
want/need a=20
    PROTO writeup as well.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>So as =
per my email=20
    of past weekend, pls do the proto writeup and send a request (from =
one=20
    of</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>the WG =
chairs) to=20
    the <A =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</A> and=20
    ask for publication as Proposed Standard.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT =
color=3D#0000ff>Pls&nbsp;do copy=20
    me.&nbsp;</FONT>&nbsp;</SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>And pls =
do only do=20
    so, after revision 8 has been posted, because that is (as per our =
email=20
    exchange</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>over the =
weekend)=20
    the one that you want published. Current ID_tracker state of this =
doc is=20
    "Revised ID needed"</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>which =
will change=20
    when new revision shows up.</FONT></SPAN></DIV>
    <P></P>
    <H4><A name=3Dncssignalingmib>PacketCable/IPCableCom NCS Signaling=20
    MIB</A><SPAN class=3D422445911-28112005><FONT color=3D#0000ff=20
    size=3D2>&nbsp;</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>I'd add =
that this is=20
    document:&nbsp; =
draft-ietf-ipcdn-pktc-signaling-09.txt</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005>&nbsp;</SPAN>Gordon Beacham, =
Satish=20
    Kumar, and Sumanth Channabasappa submitted version 09 of the NCS =
Signaling=20
    MIB draft, to address comments from the MIB doctor and various WG=20
    participants. The resolution of these comments were <A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01809.html=
">posted</A>=20
    on the mailing list. </H4>
    <P>Significant updates included changes to a number of MIB objects =
in the=20
    pktcSigDevMultiFreqToneTable, and the removal of the=20
    pktcNcsEndPntConfigTxGain and pktcNcsEndPntConfigRxGain objects. =
</P>
    <P>There were no comments concerning this internet-draft in this =
meeting.=20
    </P>
    <P>The next steps for this internet-draft are:=20
    <OL>
      <LI>The WG co-chairs will review this draft.=20
      <LI>The co-chairs will request to put the draft into the =
'Publication=20
      Requested' state. (Editor's note: does this imply a PROTO writeup =
for this=20
      draft?)&nbsp;<SPAN class=3D422445911-28112005><FONT=20
      color=3D#0000ff>&nbsp;</FONT></SPAN></LI></OL>
    <DIV><SPAN class=3D422445911-28112005><FONT =
color=3D#0000ff>Yes,&nbsp;for every=20
    "publication requested</FONT>&nbsp;<FONT color=3D#0000ff>as XX" =
(where XX is=20
    Proposed Standard, or the state you want)&nbsp; I want/need a=20
    PROTO</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff>writeup.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>This doc =
is in a=20
    weird "expired/dead" state in the ID-tracker. I am following up on =
that with=20
    secretariat to get that</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>fixed. =
Pls keep your=20
    work going to get PROTO writeup done and to send request to=20
    publish.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
    <P></P>
    <H4><A name=3Dmemmib>PacketCable/IPCableCom Management Event =
MIB</A><SPAN=20
    class=3D422445911-28112005><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005></SPAN>&nbsp;</H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>I'dd add =
that this is=20
    document: <A=20
    =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventme=
ss-05.txt">draft-ietf-ipcdn-pktc-eventmess-05.txt</A></FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>also this =
doc is in a=20
    weird DEAD state in ID-tracker.</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>I am =
following up=20
    with secretrariat to get that fixed.</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005></SPAN>&nbsp;</H4>
    <P>Wim De Ketelaere, Eugene Nechamkin, and Sumanth Channabasappa =
submitted=20
    version 05 of the PacketCable/IPCableCom Management Event MIB draft, =

    responding to comments from a review by Greg Nakanishi and =
additional=20
    feedback from Randy Presuhn. The resolution of these comments were =
<A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01810.html=
">posted</A>=20
    on the mailing list. </P>
    <P>There was some discussion in the meeting about whether the event=20
    throttling objects (pktcDevEvThrottleAdminStatus,=20
    pktcDevEvThrottleThreshold, and pktcDevEvThrottleInterval) apply to =
local=20
    logging of events, or only to network transmissions of events via =
SNMP or=20
    SYSLOG messages. The current throttling MIB objects only refer to =
SNMP and=20
    SYSLOG, but pktcDevEventDescrReporting and pktcDevEvLogType refer to =
local=20
    logging. </P>
    <P>The WG recommends to add the following text to the DESCRIPTION of =

    pktcDevEvThrottleAdminStatus: "The impact of event throttling =
controls on=20
    local logging is an implementation-specific matter." </P>
    <P>Editor's note: The following DESCRIPTION of pktcDevEvLogType =
suggests=20
    that the throttling controls do NOT apply to local logging. If =
throttling of=20
    local logging is implementation-specific, then at least this =
DESCRIPTION=20
    should be revised. <XMP><FONT face=3D"Times New Roman" size=3D3>   =
pktcDevEvLogType OBJECT-TYPE=20
       SYNTAX      BITS {=20
                   local(0),=20
                   syslog (1),=20
                   trap (2),=20
                   inform (3)=20
                   }=20
       MAX-ACCESS  read-only=20
       STATUS      current=20
       DESCRIPTION=20
               "This MIB Object contains the kind of actions taken by =20
                the MTA when the event under consideration occurred.=20
   =20
                A bit with a value of 1 indicates the corresponding=20
                action was taken. Setting it to a value of 0 indicates =20
                that the corresponding action was not taken.=20
    =20
                An event may trigger one or more actions (e.g.: Syslog =20
                and SNMP) or may remain as a local event since =20
                transmissions could be disabled or inhibited as defined  =

                by the Throttle MIB Objects."=20
                =20
       ::=3D { pktcDevEventLogEntry 7 }=20
</FONT></XMP>
    <DIV><SPAN class=3D422445911-28112005><FONT face=3D"Courier New"=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT face=3D"Courier New"=20
    color=3D#0000ff>As I think I stated at the =
meeting.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT face=3D"Courier New"=20
    color=3D#0000ff>Pls be very explicit in the text of the DESCRIPTION =
clause(s)=20
    as to what&nbsp;</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT face=3D"Courier New"=20
    color=3D#0000ff>people can expect. </FONT></SPAN></DIV><XMP><FONT =
face=3DArial color=3D#0000ff></FONT></XMP>
    <P><FONT face=3D"Times New Roman" size=3D3></FONT></P>
    <P><FONT color=3D#0000ff></FONT>=20
    <P><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff>&nbsp;</FONT></SPAN><SPAN=20
    class=3D422445911-28112005>&nbsp;</SPAN>The next steps for this =
internet-draft=20
    are:=20
    <OL>
      <LI>The WG co-chairs will review this draft.=20
      <LI>The co-chairs will request to put the draft into the =
'Publication=20
      Requested' state. (Editor's note: does this imply a PROTO writeup =
for this=20
      draft?)&nbsp;<SPAN class=3D422445911-28112005><FONT=20
      color=3D#0000ff>&nbsp;</FONT></SPAN>=20
      <LI><SPAN class=3D422445911-28112005></SPAN></LI></OL>
    <DIV><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff>Yes</FONT>&nbsp;</SPAN></DIV>
    <P></P>
    <H4><A name=3Dcdmib>DOCSIS Cable Device MIB (replacing =
RFC2669)</A><SPAN=20
    class=3D422445911-28112005><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005></SPAN>&nbsp;</H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff =
size=3D2>I would add:=20
    this is document: <A=20
    =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2=
-10.txt">draft-ietf-ipcdn-device-mibv2-10.txt</A></FONT>&nbsp;</SPAN></H4=
>
    <P>Kevin Marez and Richard Woundy produced version 10 of the DOCSIS =
Cable=20
    Device MIB draft, to address comments from the AD review (Bert =
Wijnen) and=20
    from the MIB doctor review. The resolution of the AD review comments =
were <A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01808.html=
">posted</A>=20
    on the mailing list. Most comments were resolved with simple =
editorial=20
    fixes. </P>
    <P>Two significant changes in version 10 discussed in the meeting =
were the=20
    new narrative text for MIB module IMPORTs and REFERENCE clauses =
(section=20
    3.1.1), and the new narrative text discussing the persistance model =
for=20
    cable modem MIB objects (section 3.1.2). There were no significant =
comments=20
    on the IMPORT/REFERENCE narrative text, although this is different =
from the=20
    approach taken by other IPCDN internet-drafts. Bert noted that there =
was no=20
    MUST statements in the persistance model narrative, but that was OK =
since=20
    the normative persistance requirements were in the MIB object =
definitions.=20
    </P>
    <P>The next step for this internet-draft is for the IPCDN co-chairs =
(in this=20
    particular case, Jean-Francois Mule) to write a "Protocol Write-Up" =
to=20
    prepare for the IESG review process.&nbsp;<SPAN=20
    class=3D422445911-28112005><FONT =
color=3D#0000ff>&nbsp;</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</P>
    <P><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>Yep, the =
so called=20
    PROTO write up.</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>And that =
normally=20
    comes in with&nbsp;a "request t</FONT>&nbsp;<FONT color=3D#0000ff> =
to publish=20
    as XX" (XX is the stds track you want, i believe PS for this=20
    doc).</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>Pls send =
to <A=20
    href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</A> =
and cc:=20
    myself.</FONT></SPAN></P>
    <P><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff></FONT></SPAN>&nbsp;</P>
    <H4><A name=3Drfimib>DOCSIS RFIv2 MIB (replacing RFC2670)</A><SPAN=20
    class=3D422445911-28112005><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></H4>
    <H4><SPAN class=3D422445911-28112005><FONT color=3D#0000ff =
size=3D2>This is=20
    document: <A=20
    =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2=
-14.txt">draft-ietf-ipcdn-docs-rfmibv2-14.txt</A></FONT>&nbsp;</SPAN></H4=
>
    <P>Eduardo Cardona produced version 14 of the DOCSIS RFIv2 MIB, in =
response=20
    to comments from the <A=20
    =
href=3D"http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01694.html=
">AD=20
    review</A> (Bert Wijnen). </P>
    <P>There were no comments concerning this internet-draft in this =
meeting.=20
    </P>
    <P>The next steps for this internet-draft are:=20
    <OL>
      <LI>The WG co-chairs will review this draft.=20
      <LI>The co-chairs will request to put the draft into the =
'Publication=20
      Requested' state. (Editor's note: does this imply a PROTO writeup =
for this=20
      draft?)&nbsp;<SPAN class=3D422445911-28112005><FONT=20
      color=3D#0000ff>&nbsp;</FONT></SPAN>=20
      <LI><SPAN class=3D422445911-28112005></SPAN></LI></OL>
    <DIV><SPAN class=3D422445911-28112005><FONT color=3D#0000ff>Yep, see =

    above</FONT></SPAN></DIV>
    <DIV><SPAN class=3D422445911-28112005></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D422445911-28112005><FONT=20
    color=3D#0000ff>Bert</FONT>&nbsp;</SPAN></DIV>
    <P></P>
    <H4><A name=3Dnextsteps>IPCDN Next Steps</A></H4>
    <P>The co-chairs will review plans for promoting, finalizing, and =
reviewing=20
    current IPCDN MIBs, with a focus on the DOCSIS and =
PacketCable/IPCableCom=20
    MIB internet-drafts. </P>
    <H4>Co-chairs:</H4>
    <P>Richard Woundy =
&lt;Richard_Woundy@cable.comcast.com&gt;<BR>Jean-Francois=20
    Mule' &lt;jf.mule@cablelabs.com&gt;=20
</P></SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C6003A.85DA07DE--


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

--===============2059425066==--




From ipcdn-bounces@ietf.org Wed Dec 14 09:47:54 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmXv8-0002YW-CG; Wed, 14 Dec 2005 09:47:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXv4-0002WN-1k
	for ipcdn@megatron.ietf.org; Wed, 14 Dec 2005 09:47:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04696
	for <ipcdn@ietf.org>; Wed, 14 Dec 2005 09:46:51 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmXwC-0001SI-69
	for ipcdn@ietf.org; Wed, 14 Dec 2005 09:49:03 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBEElPxF028958; 
	Wed, 14 Dec 2005 08:47:26 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BR4NQM>; Wed, 14 Dec 2005 15:47:24 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508DA0CD7@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>
Subject: RE: [ipcdn] Request for publication and proto write-up for draft-
	ietf-ipcdn-device-mibv2-10.txt on the standards track
Date: Wed, 14 Dec 2005 14:29:22 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 5a985ed7c9101086bea2cd7287e9f83a
Cc: kevin.marez@motorola.com,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>,
	ipcdn@ietf.org
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="===============1080957937=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1080957937==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C600B2.6451D5C2"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C600B2.6451D5C2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

OK, I have requested IETF Last Call.
I have also created an RFC-Editor note (to address my remaining comment =
that
I reported earlier):
=20
  Note to RFC Editor
=20
  - Pls fix the DESCRIPTION clause of the MODULE-IDENTITY (page 17):
=20
  OLD:
                Copyright (C) The Internet Society (2005). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself.
                Supplementary information may be available at:
                http://www.ietf.org/copyrights/ianamib.html =
<http://www.ietf.org/copyrights/ianamib.html> ."
  NEW:
                Copyright (C) The Internet Society (2005). The initial
                version of this MIB module was published in RFC XXXX;
                for full legal notices see the RFC itself."
=20
=20
If all goes well, we may be able to put this doc on Jan 5 IESG =
telechat.
=20
Bert
=20

-----Original Message-----
From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]
Sent: Friday, December 09, 2005 17:41
To: Wijnen, Bert (Bert); iesg-secretary@ietf.org
Cc: Richard Woundy @ Comcast; kevin.marez@motorola.com; ipcdn@ietf.org
Subject: [ipcdn] Request for publication and proto write-up for =
draft-ietf-ipcdn-device-mibv2-10.txt on the standards track


Bert and all,
=20
   This note is the request for publication and proto write-up for=20
draft-ietf-ipcdn-device-mibv2-10.txt.=20
=20
Let us know if you have any questions or concerns with the above by
sending txt to the ipcdn list. Thank you Rich and Kevin for your=20
continued efforts and big thanks to Randy, Bert et al. for the detailed
and constructive MIB doctor and expert reviews.
=20
Jean-Fran=E7ois
jfm@cablelabs.com
IPCDN co-chair.
=20
The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used for the IPCDN Cable Device MIB v2 Internet-Draft.
=20
Here is the proposed PROTO writeup for:
Cable Device Management Information Base for Data-Over-Cable Service
Interface Specification Compliant Cable Modems and Cable Modem
                          Termination Systems
                    draft-ietf-ipcdn-device-mibv2-10
=20
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-10.txt
=20
=20
Requested Publication Status: Proposed Standard
Obsoletes: RFC 2669
PROTO shepherd: Jean-Francois Mule (IPCDN WG co-chair)
------------------------------------------------------------------------=

=20
   1.a) Have the chairs personally reviewed this version of the =
Internet
        Draft (ID), and in particular, do they believe this ID is ready
        to forward to the IESG for publication?
=20
Yes.
One of the 2 IPCDN co-chairs is a co-author and the other is the PROTO
shepherd writing this note. Both have reviewed this version of the ID.
Based on the WG comments, MIB doctors & AD review comments, the ID is
believed to be ready for publication.
=20
=20
   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?
=20
Yes, reviews from both subject-matter experts that are WG members and
MIB doctors who provided valuable comments to improve the quality of
the MIB module.
=20
=20
        Do you have any concerns about the
        depth or breadth of the reviews that have been performed?
=20
No, given the time this ID has been in existence and the number of
revisions due to comments.
=20
=20
   1.c) Do you have concerns that the document needs more review from a
        particular (broader) perspective (e.g., security, operational
        complexity, someone familiar with AAA, etc.)?
=20
No.
=20
   1.d) Do you have any specific concerns/issues with this document =
that
        you believe the ADs and/or IESG should be aware of?  For
        example, perhaps you are uncomfortable with certain parts of =
the
        document, or have concerns whether there really is a need for
        it.  In any event, if your issues have been discussed in the WG
        and the WG has indicated it that it still wishes to advance the
        document, detail those concerns in the write-up.
=20
No. The IETF 63 meeting was dedicated to addressing all the remaining
WG comments and the draft update does close those open issues. No other
concerns from the PROTO shepherd.
=20
   1.e) How solid is the WG consensus behind this document? Does it
        represent the strong concurrence of a few individuals, with
        others being silent, or does the WG as a whole understand and
        agree with it?
=20
This document represents the WG consensus as a whole: the WG as a whole
understands and agrees with it.
=20
   1.f) Has anyone threatened an appeal or otherwise indicated extreme
        discontent?  If so, please summarise the areas of conflict in
        separate email to the Responsible Area Director.
=20
No. An explicit request for intent to appeal was made on the list on
November 25, 2005.
=20
   1.g) Have the chairs verified that the document adheres to all of =
the
        ID nits? (see  http://www.ietf.org/ID-Checklist.html) =
<http://www.ietf.org/ID-Checklist.html%29> .
=20
The ID nits checker (v1.82) was ran on Nov 25 2005 and found no issues.
idnits 1.82 output:
-----------
tmp/draft-ietf-ipcdn-device-mibv2-10.txt:
=20
=20
  Checking nits according to  http://www.ietf.org/ID-Checklist.html =
<http://www.ietf.org/ID-Checklist.html> :
=20
    Checking conformance with RFC 3978/3979 boilerplate...
=20
    the boilerplate looks good.
    No nits found.
=20
  Checking nits according to  =
http://www.ietf.org/ietf/1id-guidelines.txt =
<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
    No nits found.
---------------
=20
=20
   1.h) Is the document split into normative and informative =
references?
=20
Yes.
=20
        Are there normative references to IDs, where the IDs are not
        also ready for advancement or are otherwise in an unclear =
state?
        (note here that the RFC editor will not publish an RFC with
        normative references to IDs, it will delay publication until =
all
        such IDs are also ready for publication as RFCs.)
=20
No.
=20
   1.i) For Standards Track and BCP documents, the IESG approval
        announcement includes a write-up section with the following
        sections:
=20
        *    Technical Summary
=20
        *    Working Group Summary
=20
        *    Protocol Quality
Ok.
=20
   1.j) Please provide such a write-up.  Recent examples can be found =
in
        the "protocol action" announcements for approved documents.
=20
--- Technical Summary
=20
   This document is a revision of the standards track RFC 2669.
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines a basic set of managed objects for SNMP-
   based management of DOCSIS-compliant Cable Modems and Cable Modem
   Termination Systems.
=20
=20
--- Working Group Summary
=20
   The Working Group has consensus to publish this document as a
   Proposed Standard.
=20
=20
--- Protocol Quality
=20
   The MIB module has been reviewed by Randy Presuhn. The overall =
quality
   with respect to DOCSIS functionality has been reviewed by Greg White
   and Eduardo Cardona. This document has been reviewed for the IESG by
   Bert Wijnen.
=20

=20

=20

> -----Original Message-----

> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]

> Sent: Friday, November 25, 2005 4:12 PM

> To: Jean-Francois Mule; Richard Woundy @ Comcast; ipcdn@ietf.org

> Subject: RE: Advancing draft-ietf-ipcdn-device-mibv2-10.txt on the

> standards track

>=20

> I did a last check of the document.

>=20

> - In the DESCRIPTION clause of the MODULE-IDENTITY you state:

>                 Copyright (C) The Internet Society (2005). The =
initial

>                 version of this MIB module was published in RFC XXXX;

>                 for full legal notices see the RFC itself.

>                 Supplementary information may be available at:

>                 http://www.ietf.org/copyrights/ianamib.html."

>   Those last two lines can go away. This is not an IANA maintained

>   MIB module, so their copyrights have nothing to do with this.

>=20

> You can consider that as an early IETF Last Call comment, and we can

> fix it with a note to RFC-Editor if this is all that gets reported.

>=20

> So I am ready for IETF Last Call as soon as I get the PROTO report,

> which comes with a "request to publish as Proposed Standard" (and

> plx send to iesg-secretary@ietf.org and copy me).

>=20

> Bert


------_=_NextPart_001_01C600B2.6451D5C2
Content-Type: text/html;
	charset="iso-8859-1"
X-MIME-Autoconverted: from 8bit to quoted-printable by ihemail1.lucent.com id
	jBEElPxF028958
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">


<META content=3D"MSHTML 6.00.2800.1523" name=3DGENERATOR><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 89.95pt 1.0in 89.95pt; =
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
PRE {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle19 {
	mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>OK, I=20
have requested IETF Last Call.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>I have=20
also created an RFC-Editor note (to address my remaining comment=20
that</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>I=20
reported earlier):</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D828582413-14122005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>&nbsp;=20
Note to RFC Editor<BR>&nbsp;<BR>&nbsp; - Pls fix the DESCRIPTION clause o=
f the=20
MODULE-IDENTITY (page 17):</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>&nbsp;=20
OLD:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
Copyright (C) The Internet Society (2005). The=20
initial<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
version of this MIB module was published in RFC=20
XXXX;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
for full legal notices see the RFC=20
itself.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Supplementary information may be available=20
at:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
<A=20
href=3D"http://www.ietf.org/copyrights/ianamib.html">http://www.ietf.org/=
copyrights/ianamib.html</A>."<BR>&nbsp;=20
NEW:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
Copyright (C) The Internet Society (2005). The=20
initial<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
version of this MIB module was published in RFC=20
XXXX;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
for full legal notices see the RFC itself."</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D828582413-14122005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN class=3D828582413-=
14122005>If all=20
goes well, we may be able to put this doc on Jan 5 IESG=20
telechat.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D828582413-14122005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D828582413-14122005>Bert</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D828582413-14122005></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DT=
ahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jean-Francois Mule=20
  [mailto:jf.mule@cablelabs.com]<BR><B>Sent:</B> Friday, December 09, 200=
5=20
  17:41<BR><B>To:</B> Wijnen, Bert (Bert); iesg-secretary@ietf.org<BR><B>=
Cc:</B>=20
  Richard Woundy @ Comcast; kevin.marez@motorola.com;=20
  ipcdn@ietf.org<BR><B>Subject:</B> [ipcdn] Request for publication and p=
roto=20
  write-up for draft-ietf-ipcdn-device-mibv2-10.txt on the standards=20
  track<BR><BR></FONT></DIV>
  <DIV class=3DSection1><PRE><FONT face=3D"Courier New" size=3D2><SPAN st=
yle=3D"FONT-SIZE: 10pt">Bert and all,<o:p></o:p></SPAN></FONT></PRE><PRE>=
<FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>=
&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2>=
<SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; This note is the request for=
 publication and proto write-up for <o:p></o:p></SPAN></FONT></PRE><PRE><=
FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">draft-=
ietf-ipcdn-device-mibv2-10.txt. <o:p></o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp=
;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN=
 style=3D"FONT-SIZE: 10pt">Let us know if you have any questions or conce=
rns with the above by<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Co=
urier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">sending txt to the ip=
cdn list. Thank you Rich and Kevin for your <o:p></o:p></SPAN></FONT></PR=
E><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt=
">continued efforts and big thanks to Randy, Bert et al. for the detailed=
<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><=
SPAN style=3D"FONT-SIZE: 10pt">and constructive MIB doctor and expert rev=
iews.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><P=
RE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Je=
an-Fran=E7ois<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier Ne=
w" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">jfm@cablelabs.com<o:p></o:p><=
/SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt">IPCDN co-chair.<o:p></o:p></SPAN></FONT></PRE><PRE><FON=
T face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbs=
p;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPA=
N style=3D"FONT-SIZE: 10pt">The PROTO process (cf. draft-ietf-proto-wgcha=
ir-doc-shepherding-05.txt)<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">is being used for =
the IPCDN Cable Device MIB v2 Internet-Draft.<o:p></o:p></SPAN></FONT></P=
RE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10p=
t"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" s=
ize=3D2><SPAN style=3D"FONT-SIZE: 10pt">Here is the proposed PROTO writeu=
p for:<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=
=3D2><SPAN style=3D"FONT-SIZE: 10pt">Cable Device Management Information =
Base for Data-Over-Cable Service<o:p></o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Interface =
Specification Compliant Cable Modems and Cable Modem<o:p></o:p></SPAN></F=
ONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SI=
ZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nb=
sp;&nbsp;&nbsp;Termination Systems<o:p></o:p></SPAN></FONT></PRE><PRE><FO=
NT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-ipcdn-device-mibv2-10<o:p></=
o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN st=
yle=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT f=
ace=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">ftp://ftp.ie=
tf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-10.txt<o:p></o:p></S=
PAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"=
FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"=
Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></=
SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt">Requested Publication Status: Proposed Standard<o:p></o=
:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN sty=
le=3D"FONT-SIZE: 10pt">Obsoletes: RFC 2669<o:p></o:p></SPAN></FONT></PRE>=
<PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">=
PROTO shepherd: <st1:PersonName w:st=3D"on">Jean-Francois Mule</st1:Perso=
nName> (IPCDN WG co-chair)<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" color=3Dslateblue size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
COLOR: slateblue">-------------------------------------------------------=
-----------------</SPAN></FONT><o:p></o:p></PRE><PRE><FONT face=3D"Courie=
er New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN>=
</FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT=
-SIZE: 10pt">&nbsp;&nbsp; 1.a) Have the chairs personally reviewed this v=
ersion of the Internet<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"C=
ourier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Draft (ID), and in particular, do they believe thi=
s ID is ready<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier Ne=
w" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; to forward to the IESG for publication?<o:p></o:p></SPAN></=
FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-S=
IZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courie=
r New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Yes.<o:p></o:p></SPAN></F=
ONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SI=
ZE: 10pt">One of the 2 IPCDN co-chairs is a co-author and the other is th=
e PROTO<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" siz=
e=3D2><SPAN style=3D"FONT-SIZE: 10pt">shepherd writing this note. Both ha=
ve reviewed this version of the ID.<o:p></o:p></SPAN></FONT></PRE><PRE><F=
ONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Based o=
n the WG comments, MIB doctors &amp; AD review comments, the ID is<o:p></=
o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN st=
yle=3D"FONT-SIZE: 10pt">believed to be ready for publication.<o:p></o:p><=
/SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p><=
/SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.b) Has the document had adequate review =
from both key WG members<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; and key non-WG members?<o:p></o:p></SPAN></FONT>=
</PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New=
" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Yes, reviews from both subject=
-matter experts that are WG members and<o:p></o:p></SPAN></FONT></PRE><PR=
E><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">MIB=
 doctors who provided valuable comments to improve the quality of<o:p></o=
:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN sty=
le=3D"FONT-SIZE: 10pt">the MIB module.<o:p></o:p></SPAN></FONT></PRE><PRE=
><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p=
>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2=
><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PR=
E><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do you have any concerns about th=
e<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2>=
<SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; depth or breadth of the reviews that have been performed?<o:p></o:p></S=
PAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"=
FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"=
Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">No, given the time =
this ID has been in existence and the number of<o:p></o:p></SPAN></FONT><=
/PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 1=
0pt">revisions due to comments.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT =
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;=
</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbs=
p; 1.c) Do you have concerns that the document needs more review from a<o=
:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SP=
AN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; p=
articular (broader) perspective (e.g., security, operational<o:p></o:p></=
SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complexity, =
someone familiar with AAA, etc.)?<o:p></o:p></SPAN></FONT></PRE><PRE><FON=
T face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbs=
p;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPA=
N style=3D"FONT-SIZE: 10pt">No.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT =
face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;=
</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.d) Do you have any specific conc=
erns/issues with this document that<o:p></o:p></SPAN></FONT></PRE><PRE><F=
ONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; you believe the ADs and/or IESG shoul=
d be aware of?&nbsp; For<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; example, perhaps you are uncomfortable with cert=
ain parts of the<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier=
 New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; document, or have concerns whether there really is a nee=
d for<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; it.&nbsp; In any event, if your issues have been discussed in the WG<=
o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><S=
PAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and the WG has indicated it that it still wishes to advance the<o:p></o:p=
></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=
=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document,=
 detail those concerns in the write-up.<o:p></o:p></SPAN></FONT></PRE><PR=
E><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:=
p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt">No. The IETF 63 meeting was dedicated t=
o addressing all the remaining<o:p></o:p></SPAN></FONT></PRE><PRE><FONT f=
ace=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">WG comments =
and the draft update does close those open issues. No other<o:p></o:p></S=
PAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"=
FONT-SIZE: 10pt">concerns from the PROTO shepherd.<o:p></o:p></SPAN></FON=
T></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE=
: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier N=
ew" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.e) How solid =
is the WG consensus behind this document? Does it<o:p></o:p></SPAN></FONT=
></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE:=
 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; represent the strong co=
ncurrence of a few individuals, with<o:p></o:p></SPAN></FONT></PRE><PRE><=
FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; others being silent, or does the WG =
as a whole understand and<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D=
"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; agree with it?<o:p></o:p></SPAN></FONT></PRE><PR=
E><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:=
p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt">This document represents the WG consens=
us as a whole: the WG as a whole<o:p></o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">understand=
s and agrees with it.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Co=
urier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SP=
AN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"F=
ONT-SIZE: 10pt">&nbsp;&nbsp; 1.f) Has anyone threatened an appeal or othe=
rwise indicated extreme<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"=
Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; discontent?&nbsp; If so, please summarise the are=
as of conflict in<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courie=
r New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; separate email to the Responsible Area Director.<o:p></=
o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN st=
yle=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT f=
ace=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">No. An expli=
cit request for intent to appeal was made on the list on<o:p></o:p></SPAN=
></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FON=
T-SIZE: 10pt">November 25, 2005.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp=
;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN=
 style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.g) Have the chairs verified tha=
t the document adheres to all of the<o:p></o:p></SPAN></FONT></PRE><PRE><=
FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ID nits? (see <A href=3D"http://www.=
ietf.org/ID-Checklist.html%29">http://www.ietf.org/ID-Checklist.html)</A>=
.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2>=
<SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE=
><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">The =
ID nits checker (v1.82) was ran on Nov 25 2005 and found no issues.<o:p><=
/o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN s=
tyle=3D"FONT-SIZE: 10pt">idnits 1.82 output:<o:p></o:p></SPAN></FONT></PR=
E><PRE><FONT face=3D"Courier New" color=3Dslateblue size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt; COLOR: slateblue">-----------</SPAN></FONT><o:p></o:p><=
/PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 1=
0pt">tmp/draft-ietf-ipcdn-device-mibv2-10.txt:<o:p></o:p></SPAN></FONT></=
PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" =
size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT><=
/PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 1=
0pt">&nbsp; Checking nits according to <A href=3D"http://www.ietf.org/ID-=
Checklist.html">http://www.ietf.org/ID-Checklist.html</A>:<o:p></o:p></SP=
AN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"F=
ONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"C=
ourier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; C=
hecking conformance with RFC 3978/3979 boilerplate...<o:p></o:p></SPAN></=
FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-S=
IZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courie=
r New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; the bo=
ilerplate looks good.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Co=
urier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; No=
 nits found.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New=
" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT=
></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE:=
 10pt">&nbsp; Checking nits according to <A href=3D"http://www.ietf.org/i=
etf/1id-guidelines.txt">http://www.ietf.org/ietf/1id-guidelines.txt</A>:<=
o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><S=
PAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; Nothing found here (but =
these checks do not cover all of<o:p></o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbs=
p;&nbsp; 1id-guidelines.txt yet).<o:p></o:p></SPAN></FONT></PRE><PRE><FON=
T face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbs=
p;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPA=
N style=3D"FONT-SIZE: 10pt">&nbsp; Miscellaneous warnings:<o:p></o:p></SP=
AN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"F=
ONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; None.<o:p></o:p></SPAN></FONT></PRE><P=
RE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o=
:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp; No nits found.<o:p><=
/o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" color=3Dslateblu=
e size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: slateblue">------------=
---</SPAN></FONT><o:p></o:p></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><P=
RE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o=
:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.h) Is the document split=
 into normative and informative references?<o:p></o:p></SPAN></FONT></PRE=
><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"=
><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" siz=
e=3D2><SPAN style=3D"FONT-SIZE: 10pt">Yes.<o:p></o:p></SPAN></FONT></PRE>=
<PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">=
<o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=
=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Are there normative references to IDs, where the IDs are not<o:p><=
/o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN s=
tyle=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; also =
ready for advancement or are otherwise in an unclear state?<o:p></o:p></S=
PAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"=
FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (note here th=
at the RFC editor will not publish an RFC with<o:p></o:p></SPAN></FONT></=
PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; normative references to ID=
s, it will delay publication until all<o:p></o:p></SPAN></FONT></PRE><PRE=
><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; such IDs are also ready for public=
ation as RFCs.)<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier =
New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></F=
ONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SI=
ZE: 10pt">No.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier Ne=
w" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FON=
T></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE=
: 10pt">&nbsp;&nbsp; 1.i) For Standards Track and BCP documents, the IESG=
 approval<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" s=
ize=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; announcement includes a write-up section with the following<o:p=
></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN=
 style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sec=
tions:<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=
=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE=
><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp; Technical=
 Summary<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" si=
ze=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P=
RE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10p=
t">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;*&nbsp;&nbsp;&nbsp; Working=
 Group Summary<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier N=
ew" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FO=
NT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZ=
E: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp; P=
rotocol Quality<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier =
New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">Ok.<o:p></o:p></SPAN></FONT=
></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE:=
 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier Ne=
w" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; 1.j) Please prov=
ide such a write-up.&nbsp; Recent examples can be found in<o:p></o:p></SP=
AN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"F=
ONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the "protocol =
action" announcements for approved documents.<o:p></o:p></SPAN></FONT></P=
RE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10p=
t"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><B><FONT face=3D"Courier New=
" color=3Dseagreen size=3D2><SPAN style=3D"FONT-WEIGHT: bold; FONT-SIZE: =
10pt; COLOR: seagreen">--- Technical Summary</SPAN></FONT></B><o:p></o:p>=
</PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New=
" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; This document is =
a revision of the standards track RFC 2669.<o:p></o:p></SPAN></FONT></PRE=
><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"=
>&nbsp;&nbsp; This memo defines a portion of the Management Information B=
ase (MIB)<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" s=
ize=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; for use with network=
 management protocols in the Internet community.<o:p></o:p></SPAN></FONT>=
</PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">&nbsp;&nbsp; In particular, it defines a basic set of managed objec=
ts for SNMP-<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New=
" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; based management =
of DOCSIS-compliant Cable Modems and Cable Modem<o:p></o:p></SPAN></FONT>=
</PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">&nbsp;&nbsp; Termination Systems.<o:p></o:p></SPAN></FONT></PRE><PR=
E><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:=
p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D=
2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><P=
RE><B><FONT face=3D"Courier New" color=3Dseagreen size=3D2><SPAN style=3D=
"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: seagreen">--- Working Group S=
ummary</SPAN></FONT></B><o:p></o:p></PRE><PRE><FONT face=3D"Courier New" =
size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT><=
/PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 1=
0pt">&nbsp;&nbsp; The Working Group has consensus to publish this documen=
t as a<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=
=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; Proposed Standard.<o:p>=
</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></PRE><PRE><FONT=
 face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp=
;</o:p></SPAN></FONT></PRE><PRE><B><FONT face=3D"Courier New" color=3Dsea=
green size=3D2><SPAN style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: =
seagreen">--- Protocol Quality</SPAN></FONT></B><o:p></o:p></PRE><PRE><FO=
NT face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nb=
sp;</o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New" size=3D2><SP=
AN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; The MIB module has been reviewe=
d by <st1:PersonName w:st=3D"on">Randy Presuhn</st1:PersonName>. The over=
all quality<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier New"=
 size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; with respect to DO=
CSIS functionality has been reviewed by <st1:PersonName w:st=3D"on">Greg =
White</st1:PersonName><o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"C=
ourier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp; and <st=
1:PersonName w:st=3D"on">Eduardo Cardona</st1:PersonName>. This document =
has been reviewed for the IESG by<o:p></o:p></SPAN></FONT></PRE><PRE><FON=
T face=3D"Courier New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&nbsp;&nb=
sp; Bert Wijnen.<o:p></o:p></SPAN></FONT></PRE><PRE><FONT face=3D"Courier=
 New" size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></=
FONT></PRE>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; -----Original=20
  Message-----</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; From: Wijnen, Bert (Bert)=20
  [mailto:bwijnen@lucent.com]</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; Sent: Friday, November 25, 2005 4:12=20
  PM</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; To: <st1:PersonName w:st=3D"on">Jean-Fra=
ncois=20
  Mule</st1:PersonName>; Richard Woundy @ Comcast;=20
  ipcdn@ietf.org</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; Subject: RE: Advancing=20
  draft-ietf-ipcdn-device-mibv2-10.txt on the</SPAN><o:p></o:p></FONT></P=
>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; standards track</SPAN><o:p></o:p></FONT>=
</P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; </SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; I did a last check of the=20
  document.</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; </SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; - In the DESCRIPTION clause of the=20
  MODULE-IDENTITY you state:</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Copyright (C) The Internet Society (2005). The=20
  initial</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  version of this MIB module was published in RFC=20
  XXXX;</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for full legal notices see the RFC itself.</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Supplementary information may be available at:</SPAN><o:p></o:p></FONT>=
</P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  http://www.ietf.org/copyrights/ianamib.html."</SPAN><o:p></o:p></FONT><=
/P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp; Those last two lines can go =
away.=20
  This is not an IANA maintained</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;&nbsp;&nbsp; MIB module, so their copyrig=
hts have=20
  nothing to do with this.</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; </SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; You can consider that as an early IETF L=
ast Call=20
  comment, and we can</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; fix it with a note to RFC-Editor if this=
 is all=20
  that gets reported.</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; </SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; So I am ready for IETF Last Call as soon=
 as I get=20
  the PROTO report,</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; which comes with a "request to publish a=
s=20
  Proposed Standard" (and</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; plx send to iesg-secretary@ietf.org and =
copy=20
  me).</SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt; </SPAN><o:p></o:p></FONT></P>
  <P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt">&gt;=20
Bert</SPAN><o:p></o:p></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C600B2.6451D5C2--


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

--===============1080957937==--




From ipcdn-bounces@ietf.org Wed Dec 14 09:47:54 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmXv8-0002Yv-PX; Wed, 14 Dec 2005 09:47:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXv3-0002WE-F5
	for ipcdn@megatron.ietf.org; Wed, 14 Dec 2005 09:47:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04689
	for <ipcdn@ietf.org>; Wed, 14 Dec 2005 09:46:49 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmXwC-0001SH-64
	for ipcdn@ietf.org; Wed, 14 Dec 2005 09:49:02 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBEElPgA028945; 
	Wed, 14 Dec 2005 08:47:26 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BR4NQL>; Wed, 14 Dec 2005 15:47:23 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508DA0CD6@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>, ipcdn@ietf.org,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
Date: Wed, 14 Dec 2005 14:29:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: quoted-printable
Cc: bwijnen@lucent.com, enechamkin@broadcom.com
Subject: [ipcdn] RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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@ietf.org (and copy me) a reuqest to publis,=20
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@cablelabs.com]
> Sent: Monday, December 12, 2005 19:06
> To: ipcdn@ietf.org; Richard Woundy @ Comcast
> Cc: enechamkin@broadcom.com; bwijnen@lucent.com
> Subject: RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt=20
>=20
>=20
> Rich and all,
>=20
>    Eugene and I submitted a new version of the MTA MIB. It=20
> addresses all the comments raised during the IETF 64 meeting=20
> in November and some additional feedback received from Bert.
>    See the diff at:
> http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/dr
> aft-ietf-ipcdn-pktc-mtamib-08-from-07.diff.html
>=20
>    We would like to request formal publication of this ID.
>=20
> Eugene and Jean-Fran=E7ois=20
>=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Friday, December 09, 2005 4:50 PM
> > To: i-d-announce@ietf.org
> > Cc: ipcdn@ietf.org
> > Subject: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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		: 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
> >=20
> > This memo defines a portion of the Management Information Base =
(MIB)
> >    for use with network management protocols in the=20
> 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.
> >=20
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-
> > 08.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=20
> the body of
> > 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
> 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-08.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-mtamib-08.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 Wed Dec 14 11:44:33 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmZk1-000608-8j; Wed, 14 Dec 2005 11:44:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmZjv-0005sj-DA; Wed, 14 Dec 2005 11:44:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21133;
	Wed, 14 Dec 2005 11:43:29 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EmZlA-0006dw-2H; Wed, 14 Dec 2005 11:45:44 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1EmZju-0001nc-HT; Wed, 14 Dec 2005 11:44:26 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1EmZju-0001nc-HT@newodin.ietf.org>
Date: Wed, 14 Dec 2005 11:44:26 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipcdn@ietf.org
Subject: [ipcdn] Last Call: 'Cable Device Management Information Base for 
 Data-Over-Cable Service Interface Specification Compliant Cable Modems 
 and Cable Modem Termination Systems' to Proposed Standard 
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

The IESG has received a request from the IP over Cable Data Network WG to 
consider the following document:

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

This document obsoletes RFC2669.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-12-28.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-10.txt


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



From ipcdn-bounces@ietf.org Thu Dec 15 18:27:35 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En2Vb-0005P7-Mb; Thu, 15 Dec 2005 18:27:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En2VZ-0005OG-Mc
	for ipcdn@megatron.ietf.org; Thu, 15 Dec 2005 18:27:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01227
	for <ipcdn@ietf.org>; Thu, 15 Dec 2005 18:26:34 -0500 (EST)
Received: from mms1.broadcom.com ([216.31.210.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En2X0-00033H-Ug
	for ipcdn@ietf.org; Thu, 15 Dec 2005 18:29:06 -0500
Received: from 10.10.64.121 by mms1.broadcom.com with SMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.0)); Thu, 15 Dec 2005 15:26:45 -0800
X-Server-Uuid: F962EFE0-448C-40EE-8100-87DF498ED0EA
Received: from mail-irva-8.broadcom.com ([10.10.64.221]) by
	mail-irva-1.broadcom.com (Post.Office MTA v3.5.3 release 223 ID#
	0-72233U7200L2200S0V35) with ESMTP id com; Thu, 15 Dec 2005 15:26:42
	-0800
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.5.6-GR) with ESMTP
	id CIW11240; Thu, 15 Dec 2005 15:26:19 -0800 (PST)
Received: from NT-SJCA-0751.brcm.ad.broadcom.com (nt-sjca-0751
	[10.16.192.221]) by mail-sj1-12.sj.broadcom.com (Postfix) with ESMTP id
	6098920502; Thu, 15 Dec 2005 15:26:19 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Dec 2005 15:26:12 -0800
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F48564395DCC@NT-SJCA-0751.brcm.ad.broadcom.com>
Thread-Topic: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt
Thread-Index: AcYAvVM8TQO0hof4QrSAWdf1QGAGBQBDvwzw
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, ipcdn@ietf.org
X-WSS-ID: 6FBF243F3GG4298497-01-01
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Content-Transfer-Encoding: quoted-printable
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
Subject: [ipcdn] RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   3.7 X.509 Certificates Dependencies

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

The pktcMtaDevRealmOrgName MIB Object, defined in this document,=20
should contain OrganizationName attribute in the X.509 certificate of=20
the Telephony Service Provider. As per RFC 3280 [RFC3280], X.509=20
attributes are defined as "UTF8String" for all certificates issued=20
after December 31, 2003. RFC 3280 refers to RFC 2279 [RFC2279]=20
for the definition of the "UTF8String" type. Further, currently obsolete =

RFC 2279 requires that each "UTF8String" encoded character may contain=20
up to 6 octets, whereas the currently active RFC 3629 [RFC3629] requires =

up to 4 octets for each "UTF8String" encoded character. To stay =
consistent=20
with RFC 3280, this document defines the length of the=20
pktcMtaDevRealmOrgName MIB Object based on RFC 2279 rather than based=20
on RFC 3629.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

2. Add to Section 7 "Informative References" the following reference (in =
front of all other references in this section):

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
             RFC 2279, January 1998.=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

If there are no objections during today, we'll modify the MTA draft-08 =
with two modifications proposed above and submit a new revision 09.

Regards,

Jean-Francois & Eugene.
=20

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
Sent: Wednesday, December 14, 2005 5:29 AM
To: Jean-Francois Mule; ipcdn@ietf.org; Richard Woundy @ Comcast
Cc: Eugene Nechamkin; bwijnen@lucent.com
Subject: 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@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@cablelabs.com]
> Sent: Monday, December 12, 2005 19:06
> To: ipcdn@ietf.org; Richard Woundy @ Comcast
> Cc: enechamkin@broadcom.com; bwijnen@lucent.com
> Subject: RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt
>=20
>=20
> Rich and all,
>=20
>    Eugene and I submitted a new version of the MTA MIB. It addresses=20
> all the comments raised during the IETF 64 meeting in November and=20
> some additional feedback received from Bert.
>    See the diff at:
> http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/dr
> aft-ietf-ipcdn-pktc-mtamib-08-from-07.diff.html
>=20
>    We would like to request formal publication of this ID.
>=20
> Eugene and Jean-Fran=E7ois
>=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Friday, December 09, 2005 4:50 PM
> > To: i-d-announce@ietf.org
> > Cc: ipcdn@ietf.org
> > Subject: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.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		: 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
> >=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 defines a basic set of managed objects for
> >    SNMP-based management of PacketCable and IPCablecom compliant
> >    Multimedia Terminal Adapter devices.
> >=20
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-
> > 08.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=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-mtamib-08.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-mtamib-08.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=20
> implementation to automatically retrieve the ASCII version of the=20
> Internet-Draft.



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



From ipcdn-bounces@ietf.org Thu Dec 15 19:23:10 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En3NO-0004ts-1d; Thu, 15 Dec 2005 19:23:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En3NK-0004qW-OO
	for ipcdn@megatron.ietf.org; Thu, 15 Dec 2005 19:23:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05619
	for <ipcdn@ietf.org>; Thu, 15 Dec 2005 19:22:06 -0500 (EST)
Received: from pop-borzoi.atl.sa.earthlink.net ([207.69.195.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En3Op-0004p6-BX
	for ipcdn@ietf.org; Thu, 15 Dec 2005 19:24:39 -0500
Received: from h-68-165-4-210.snvacaid.dynamic.covad.net ([68.165.4.210]
	helo=oemcomputer)
	by pop-borzoi.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1En3NB-0000lX-00; Thu, 15 Dec 2005 19:22:57 -0500
Message-ID: <002201c601d7$945606a0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Eugene Nechamkin" <enechamkin@broadcom.com>,
	"Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>, <ipcdn@ietf.org>
References: <9C5C578DD43AFD4EA7A9F0BDB2F48564395DCC@NT-SJCA-0751.brcm.ad.broadcom.com>
Subject: Re: [ipcdn] RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt
Date: Thu, 15 Dec 2005 16:28:02 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id TAA05619
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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 SnmpAdminStrin=
g
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
assigned any code points above 10ffff.

Randy

----- Original Message -----=20
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; <ipcdn@ietf.org>
Cc: "Jean-Francois Mule" <jf.mule@cablelabs.com>; "Richard Woundy @ Comca=
st" <Richard_woundy@cable.comcast.com>
Sent: Thursday, December 15, 2005 3:26 PM
Subject: [ipcdn] 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 RFC=
2279 for the definition of the "UTF8String" type. Further,
as per RFC2279, each "UTF8String" encoded character may contain up to 6 o=
ctets, 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 foll=
owing modifications of the MTA draft:

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   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
after December 31, 2003. RFC 3280 refers to RFC 2279 [RFC2279]
for the definition of the "UTF8String" type. Further, currently obsolete
RFC 2279 requires that each "UTF8String" encoded character may contain
up to 6 octets, whereas the currently active RFC 3629 [RFC3629] requires
up to 4 octets for each "UTF8String" encoded character. To stay consisten=
t
with RFC 3280, this document defines the length of the
pktcMtaDevRealmOrgName MIB Object based on RFC 2279 rather than based
on RFC 3629.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

2. Add to Section 7 "Informative References" the following reference (in =
front of all other references in this section):

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
             RFC 2279, January 1998.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

If there are no objections during today, we'll modify the MTA draft-08 wi=
th two modifications proposed above and submit a new
revision 09.

Regards,

Jean-Francois & Eugene.


-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, December 14, 2005 5:29 AM
To: Jean-Francois Mule; ipcdn@ietf.org; Richard Woundy @ Comcast
Cc: Eugene Nechamkin; bwijnen@lucent.com
Subject: 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 mod=
ule and probably add a citation (outside the MIB module) to
RFC3629.

Let us consider that an IETF Last Call comment.

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

Bert

> -----Original Message-----
> From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]
> Sent: Monday, December 12, 2005 19:06
> To: ipcdn@ietf.org; Richard Woundy @ Comcast
> Cc: enechamkin@broadcom.com; bwijnen@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.
>    See the diff at:
> http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/dr
> aft-ietf-ipcdn-pktc-mtamib-08-from-07.diff.html
>
>    We would like to request formal publication of this ID.
>
> Eugene and Jean-Fran=E7ois
>
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> > Sent: Friday, December 09, 2005 4:50 PM
> > To: i-d-announce@ietf.org
> > Cc: ipcdn@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
> >
> > 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-mtamib-
> > 08.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-mtamib-08.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-mtamib-08.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.



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



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



From ipcdn-bounces@ietf.org Thu Dec 15 19:46:33 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En3k1-00038y-LH; Thu, 15 Dec 2005 19:46:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En3jy-000382-TW
	for ipcdn@megatron.ietf.org; Thu, 15 Dec 2005 19:46:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07604
	for <ipcdn@ietf.org>; Thu, 15 Dec 2005 19:45:31 -0500 (EST)
Received: from pop-tawny.atl.sa.earthlink.net ([207.69.195.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En3lT-0005cI-AA
	for ipcdn@ietf.org; Thu, 15 Dec 2005 19:48:04 -0500
Received: from h-68-165-4-210.snvacaid.dynamic.covad.net ([68.165.4.210]
	helo=oemcomputer)
	by pop-tawny.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1En3jk-0005od-00; Thu, 15 Dec 2005 19:46:16 -0500
Message-ID: <000401c601da$d70eaf80$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Eugene Nechamkin" <enechamkin@broadcom.com>,
	"Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>, <ipcdn@ietf.org>
References: <9C5C578DD43AFD4EA7A9F0BDB2F48564395DCC@NT-SJCA-0751.brcm.ad.broadcom.com>
	<002201c601d7$945606a0$7f1afea9@oemcomputer>
Subject: Re: [ipcdn] RE: I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-08.txt
Date: Thu, 15 Dec 2005 16:51:18 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

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


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



From ipcdn-bounces@ietf.org Wed Dec 21 12:38:45 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep7vJ-0000c1-KV; Wed, 21 Dec 2005 12:38:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep7vI-0000Yo-54
	for ipcdn@megatron.ietf.org; Wed, 21 Dec 2005 12:38:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21045
	for <ipcdn@ietf.org>; Wed, 21 Dec 2005 12:37:38 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep7xu-0006ly-Td
	for ipcdn@ietf.org; Wed, 21 Dec 2005 12:41:29 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBLHcYWa008941; 
	Wed, 21 Dec 2005 11:38:34 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BRZJQ9>; Wed, 21 Dec 2005 18:38:32 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508F17120@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ipcdn (E-mail)" <ipcdn@ietf.org>
Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information Base 
	for Data-Over-Cable Service Interface Specification Compliant Cable
	Modem s and Cable Modem Termination Systems' to Proposed Standard 
Date: Wed, 21 Dec 2005 18:38:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: Brian Hedstrom <B.Hedstrom@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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

Authors/Editors and WG,

A comment on IETF Last Call for your consideration and
possible action.

Not sure that Brian is subscribed to IPCDN list, so pls DO
copy him on any responses.

Bert



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of
> Brian Hedstrom
> Sent: Monday, December 19, 2005 20:23
> To: iesg@ietf.org
> Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information
> Base for Data-Over-Cable Service Interface Specification 
> Compliant Cable
> Modems and Cable Modem Termination Systems' to Proposed Standard 
> 
> 
> IETF:
> 
> Regarding this object:
>    docsDevEvSyslogAddress OBJECT-TYPE
>            SYNTAX      InetAddress
>            MAX-ACCESS  read-write
>            STATUS      current
>            DESCRIPTION
>                "The internet address of the Syslog server.  If the
>                 address of the server is set to any of the zero length
>                 string, the 0.0.0.0 V4 address or the 0: V6 address,
>                 syslog transmission is inhibited.  By default at agent
>                 boot, this object returns the zero length string."
>            ::= { docsDevEvent 10 }
> 
> This object does not support provisioning multiple Syslog 
> servers within
> the CM.  However, DHCP Option 7 (log server option, as 
> defined in DOCSIS
> 2.0 Radio Frequency Interface Specification 
> [CM-SP-RFIv2.0-I09-050812])
> does allow for specification of multiple log server addresses so
> although they cannot all be instrumented it is possible to provide the
> CM with multiple log server addresses. It seems reasonable to 
> extend the
> docsDevEvSyslogAddress object to support multiple IP 
> addresses but I do
> not know if this was already addressed and rejected during the
> development of this Internet draft. The change could potentially mean
> deprecating docsDevEvSyslogAddress and replacing it with a 
> table object
> which supports Row Creation or statically creates n-number of rows. A
> similar approach was taken in CableHome with the definition of
> cabhCdpWanDnsServerTable (CABH-CDP-MIB). The structure of
> cabhCdpWanDnsServerTable identifies an order of preference (primary,
> secondary, or tertiary) for each entry.  See below:
> cabhCdpWanDnsServerTable OBJECT-TYPE
>     SYNTAX SEQUENCE OF CabhCdpWanDnsServerEntry
>     MAX-ACCESS not-accessible
>     STATUS current
>     DESCRIPTION
>             "This table contains the IP addresses of cable network and
>             Internet DNS servers, in the order of preference in which
>             the PS's CNP will query them, when it cannot resolve a DNS
>             query using local information. Entries in this table are
>             updated with the information contained in DHCP Option 6,
>             received during both the WAN-Man and WAN-Data IP 
>             acquisition processes."
>     ::= { cabhCdpAddr 3 }
> 
> cabhCdpWanDnsServerEntry OBJECT-TYPE
>     SYNTAX      CabhCdpWanDnsServerEntry
>     MAX-ACCESS  not-accessible
>     STATUS     current
>     DESCRIPTION
>             "List of cable network and Internet DNS servers."
>     INDEX { cabhCdpWanDnsServerOrder }
>     ::= { cabhCdpWanDnsServerTable 1 }
> 
> CabhCdpWanDnsServerEntry ::= SEQUENCE {
>     cabhCdpWanDnsServerOrder  INTEGER,
>     cabhCdpWanDnsServerIpType InetAddressType,
>     cabhCdpWanDnsServerIp     InetAddress
>     }
> 
> cabhCdpWanDnsServerOrder OBJECT-TYPE
>     SYNTAX      INTEGER {
>                     primary(1),
>                     secondary(2),
>                     tertiary(3)
>                 }
>     MAX-ACCESS  not-accessible
>     STATUS      current
>     DESCRIPTION
>             "The order of preference for cable network and 
> Internet DNS
>             servers, as listed in DHCP option 6 (Domain Server). Any
>             time the CDC receives valid IP address information within
>             DHCP Option 6, as part of lease acquisition or renewal of
>             a WAN-Man or WAN-Data IP, it must update this information
>             into this table.  As entries in DHCP Option 6 are 
> listed in
>             order of preference, the highest priority entry in DHCP
>             Option 6 must correspond to the row with a
>             cabhCdpWanDnsServerOrder with a value of 1. If DHCP
>             Option 6 contains 1 valid IP address, the PS MUST update
>             the row with a cabhCdpWanDnsServerOrder value of 1 and
>             MUST NOT modify rows with 
>             cabhCdpWanDnsServerOrder values of 2 & 3
>             (if they exist). If DHCP Option 6 contains 2 valid
>             IP addresses, the PS MUST update the rows with
>             cabhCdpWanDnsServerOrder values of 1 and 2
>             and MUST NOT modify the row with cabhCdpWanDnsServerOrder
>             value of 3 (if it exists). If DHCP Option 6 contains 3
>             valid IP addresses, the PS MUST update rows with 
>             cabhCdpWanDnsServerOrder values of 1, 2, and 3.  
>             Any DNS server information included in DHCP Option 6
>             beyond primary, secondary and tertiary will not be
>             represented in this table."
>     ::= { cabhCdpWanDnsServerEntry 1 }
> 
> cabhCdpWanDnsServerIpType OBJECT-TYPE
>     SYNTAX      InetAddressType
>     MAX-ACCESS read-only
>     STATUS current
>     DESCRIPTION
>             "This parameter indicates the IP address type of a
>             WAN DNS server."
>     DEFVAL { ipv4 }
>     ::= { cabhCdpWanDnsServerEntry 2 }
> 
> cabhCdpWanDnsServerIp OBJECT-TYPE
>     SYNTAX      InetAddress
>     MAX-ACCESS  read-only
>     STATUS      current
>     DESCRIPTION
>             "This parameter indicates the IP address of a WAN DNS
>             server. The type of this address is specified by 
>             cabhCdpWanDnsServerIpType."
>     ::= { cabhCdpWanDnsServerEntry 3 }
> 
> Thanks,
> Brian Hedstrom
> Senior Engineer, Operation Support Systems
> Broadband Access
> CableLabs, Inc.
> 858 Coal Creek Circle
> Louisville, CO 80027
> Direct: 303.661.3829
> eFax: 303.664.8120
> b.hedstrom@cablelabs.com
> 
>   
> -----Original Message-----
> From: The IESG [mailto:iesg-secretary@ietf.org] 
> Sent: Wednesday, December 14, 2005 9:44 AM
> To: IETF-Announce
> Cc: ipcdn@ietf.org
> Subject: [ipcdn] Last Call: 'Cable Device Management Information Base
> for Data-Over-Cable Service Interface Specification Compliant Cable
> Modems and Cable Modem Termination Systems' to Proposed Standard 
> 
> The IESG has received a request from the IP over Cable Data Network WG
> to 
> consider the following document:
> 
> - 'Cable Device Management Information Base for 
> Data-Over-Cable Service 
>    Interface Specification Compliant Cable Modems and Cable Modem
> Termination 
>    Systems '
>    <draft-ietf-ipcdn-device-mibv2-10.txt> as a Proposed Standard
> 
> This document obsoletes RFC2669.
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-12-28.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mi
bv2-10.txt


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


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



From ipcdn-bounces@ietf.org Wed Dec 21 15:06:31 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpAEJ-0005oP-AH; Wed, 21 Dec 2005 15:06:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpAEH-0005nb-A4
	for ipcdn@megatron.ietf.org; Wed, 21 Dec 2005 15:06:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13572
	for <ipcdn@ietf.org>; Wed, 21 Dec 2005 15:05:24 -0500 (EST)
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpACf-0004cE-Q7
	for ipcdn@ietf.org; Wed, 21 Dec 2005 15:04:50 -0500
Received: from ([10.20.9.174])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.15748167;
	Wed, 21 Dec 2005 15:01:22 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.211); Wed, 21 Dec 2005 15:01:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information Base for
	Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed
	Standard 
Date: Wed, 21 Dec 2005 15:00:55 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF493@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: [ipcdn] Last Call: 'Cable Device Management Information Base for
	Data-Over-Cable Service Interface Specification Compliant
	CableModem s and Cable Modem Termination Systems' to Proposed
	Standard 
Thread-Index: AcYGVijuijh7uwbkQoyThfZ2WaZyzgAEMNiQ
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Brian Hedstrom" <B.Hedstrom@CableLabs.com>,
	"Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>
X-OriginalArrivalTime: 21 Dec 2005 20:01:21.0923 (UTC)
	FILETIME=[508A9530:01C60669]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 187ae6c2eea74946c0ab707161f6256d
Content-Transfer-Encoding: quoted-printable
Cc: "Ipcdn \(E-mail\)" <ipcdn@ietf.org>, "Woundy,
	Richard" <Richard_Woundy@cable.comcast.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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

Brian, Bert,

I need some help from the IPCDN working group to resolve this Last Call
objection.

The latest DOCSIS RFI specification,
<http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-051209.pdf>,
annex D.1.1, specifies the use of five standard DHCP options:

* Option code 1 (Subnet Mask)
* Option code 2 (Time Offset)
* Option code 3 (Router Option)
* Option code 4 (Time Server Option)
* Option code 7 (Log Server Option)

Looking at RFC 2132, =
<http://www.ietf.org/rfc/rfc2132.txt?number=3D2132>,
it becomes obvious that DHCP options 1 and 2 are single-valued options,
and DHCP options 3, 4 and 7 are potentially multi-valued options.

So it would seem that if we are worried about multi-valued DHCP options,
we should be just as concerned about multiple time servers (e.g.
docsDevServerTimeAddress) as about multiple SYSLOG servers (e.g.
docsDevEvSyslogAddress).

RFC 2669 (the original Cable Device MIB) was published August 1999, and
RFC 2132 was published March 1997. So the MIB module restrictions for a
single time server and SYSLOG server has been around for over six years,
without an objection until now. Is this a real problem, or a theoretical
problem?

I can think of three reactions to this objection: (1) no changes, (2)
clarify the relevant MIB objects so that they report the *first* DHCP
option value if the DHCP option is multi-valued, or (3) change the MIB
module to add tables to capture (multiple) Time Servers and/or SYSLOG
servers.

-- Rich

-----Original Message-----
From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf
Of Wijnen, Bert (Bert)
Sent: Wednesday, December 21, 2005 12:39 PM
To: Ipcdn (E-mail)
Cc: Brian Hedstrom
Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information
Base for Data-Over-Cable Service Interface Specification Compliant
CableModem s and Cable Modem Termination Systems' to Proposed Standard=20


Authors/Editors and WG,

A comment on IETF Last Call for your consideration and
possible action.

Not sure that Brian is subscribed to IPCDN list, so pls DO
copy him on any responses.

Bert



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of

> Brian Hedstrom
> Sent: Monday, December 19, 2005 20:23
> To: iesg@ietf.org
> Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information=20
> Base for Data-Over-Cable Service Interface Specification Compliant=20
> Cable Modems and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> IETF:
>=20
> Regarding this object:
>    docsDevEvSyslogAddress OBJECT-TYPE
>            SYNTAX      InetAddress
>            MAX-ACCESS  read-write
>            STATUS      current
>            DESCRIPTION
>                "The internet address of the Syslog server.  If the
>                 address of the server is set to any of the zero length
>                 string, the 0.0.0.0 V4 address or the 0: V6 address,
>                 syslog transmission is inhibited.  By default at agent
>                 boot, this object returns the zero length string."
>            ::=3D { docsDevEvent 10 }
>=20
> This object does not support provisioning multiple Syslog
> servers within
> the CM.  However, DHCP Option 7 (log server option, as=20
> defined in DOCSIS
> 2.0 Radio Frequency Interface Specification=20
> [CM-SP-RFIv2.0-I09-050812])
> does allow for specification of multiple log server addresses so
> although they cannot all be instrumented it is possible to provide the
> CM with multiple log server addresses. It seems reasonable to=20
> extend the
> docsDevEvSyslogAddress object to support multiple IP=20
> addresses but I do
> not know if this was already addressed and rejected during the
> development of this Internet draft. The change could potentially mean
> deprecating docsDevEvSyslogAddress and replacing it with a=20
> table object
> which supports Row Creation or statically creates n-number of rows. A
> similar approach was taken in CableHome with the definition of
> cabhCdpWanDnsServerTable (CABH-CDP-MIB). The structure of
> cabhCdpWanDnsServerTable identifies an order of preference (primary,
> secondary, or tertiary) for each entry.  See below:
> cabhCdpWanDnsServerTable OBJECT-TYPE
>     SYNTAX SEQUENCE OF CabhCdpWanDnsServerEntry
>     MAX-ACCESS not-accessible
>     STATUS current
>     DESCRIPTION
>             "This table contains the IP addresses of cable network and
>             Internet DNS servers, in the order of preference in which
>             the PS's CNP will query them, when it cannot resolve a DNS
>             query using local information. Entries in this table are
>             updated with the information contained in DHCP Option 6,
>             received during both the WAN-Man and WAN-Data IP=20
>             acquisition processes."
>     ::=3D { cabhCdpAddr 3 }
>=20
> cabhCdpWanDnsServerEntry OBJECT-TYPE
>     SYNTAX      CabhCdpWanDnsServerEntry
>     MAX-ACCESS  not-accessible
>     STATUS     current
>     DESCRIPTION
>             "List of cable network and Internet DNS servers."
>     INDEX { cabhCdpWanDnsServerOrder }
>     ::=3D { cabhCdpWanDnsServerTable 1 }
>=20
> CabhCdpWanDnsServerEntry ::=3D SEQUENCE {
>     cabhCdpWanDnsServerOrder  INTEGER,
>     cabhCdpWanDnsServerIpType InetAddressType,
>     cabhCdpWanDnsServerIp     InetAddress
>     }
>=20
> cabhCdpWanDnsServerOrder OBJECT-TYPE
>     SYNTAX      INTEGER {
>                     primary(1),
>                     secondary(2),
>                     tertiary(3)
>                 }
>     MAX-ACCESS  not-accessible
>     STATUS      current
>     DESCRIPTION
>             "The order of preference for cable network and
> Internet DNS
>             servers, as listed in DHCP option 6 (Domain Server). Any
>             time the CDC receives valid IP address information within
>             DHCP Option 6, as part of lease acquisition or renewal of
>             a WAN-Man or WAN-Data IP, it must update this information
>             into this table.  As entries in DHCP Option 6 are=20
> listed in
>             order of preference, the highest priority entry in DHCP
>             Option 6 must correspond to the row with a
>             cabhCdpWanDnsServerOrder with a value of 1. If DHCP
>             Option 6 contains 1 valid IP address, the PS MUST update
>             the row with a cabhCdpWanDnsServerOrder value of 1 and
>             MUST NOT modify rows with=20
>             cabhCdpWanDnsServerOrder values of 2 & 3
>             (if they exist). If DHCP Option 6 contains 2 valid
>             IP addresses, the PS MUST update the rows with
>             cabhCdpWanDnsServerOrder values of 1 and 2
>             and MUST NOT modify the row with cabhCdpWanDnsServerOrder
>             value of 3 (if it exists). If DHCP Option 6 contains 3
>             valid IP addresses, the PS MUST update rows with=20
>             cabhCdpWanDnsServerOrder values of 1, 2, and 3. =20
>             Any DNS server information included in DHCP Option 6
>             beyond primary, secondary and tertiary will not be
>             represented in this table."
>     ::=3D { cabhCdpWanDnsServerEntry 1 }
>=20
> cabhCdpWanDnsServerIpType OBJECT-TYPE
>     SYNTAX      InetAddressType
>     MAX-ACCESS read-only
>     STATUS current
>     DESCRIPTION
>             "This parameter indicates the IP address type of a
>             WAN DNS server."
>     DEFVAL { ipv4 }
>     ::=3D { cabhCdpWanDnsServerEntry 2 }
>=20
> cabhCdpWanDnsServerIp OBJECT-TYPE
>     SYNTAX      InetAddress
>     MAX-ACCESS  read-only
>     STATUS      current
>     DESCRIPTION
>             "This parameter indicates the IP address of a WAN DNS
>             server. The type of this address is specified by=20
>             cabhCdpWanDnsServerIpType."
>     ::=3D { cabhCdpWanDnsServerEntry 3 }
>=20
> Thanks,
> Brian Hedstrom
> Senior Engineer, Operation Support Systems
> Broadband Access
> CableLabs, Inc.
> 858 Coal Creek Circle
> Louisville, CO 80027
> Direct: 303.661.3829
> eFax: 303.664.8120
> b.hedstrom@cablelabs.com
>=20
>  =20
> -----Original Message-----
> From: The IESG [mailto:iesg-secretary@ietf.org]
> Sent: Wednesday, December 14, 2005 9:44 AM
> To: IETF-Announce
> Cc: ipcdn@ietf.org
> Subject: [ipcdn] Last Call: 'Cable Device Management Information Base
> for Data-Over-Cable Service Interface Specification Compliant Cable
> Modems and Cable Modem Termination Systems' to Proposed Standard=20
>=20
> The IESG has received a request from the IP over Cable Data Network WG

> to consider the following document:
>=20
> - 'Cable Device Management Information Base for
> Data-Over-Cable Service=20
>    Interface Specification Compliant Cable Modems and Cable Modem
> Termination=20
>    Systems '
>    <draft-ietf-ipcdn-device-mibv2-10.txt> as a Proposed Standard
>=20
> This document obsoletes RFC2669.
>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action.  Please send any comments to the=20
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-12-28.
>=20
> The file can be obtained via=20
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mi
bv2-10.txt


_______________________________________________
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

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



From ipcdn-bounces@ietf.org Wed Dec 21 15:50:02 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpAuQ-0006Hx-HW; Wed, 21 Dec 2005 15:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpAuO-0006He-EL
	for ipcdn@megatron.ietf.org; Wed, 21 Dec 2005 15:50:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19437
	for <ipcdn@ietf.org>; Wed, 21 Dec 2005 15:48:55 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpAx5-0006eP-1j
	for ipcdn@ietf.org; Wed, 21 Dec 2005 15:52:47 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.13.4/8.13.4) with ESMTP id jBLKnfic008420;
	Wed, 21 Dec 2005 13:49:41 -0700 (MST)
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: RE: [ipcdn] Last Call: 'Cable Device Management Information Base
	forData-Over-Cable Service Interface Specification
	CompliantCableModem s and Cable Modem Termination Systems' to
	ProposedStandard 
Date: Wed, 21 Dec 2005 13:49:41 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804011F629E@srvxchg.cablelabs.com>
Thread-Topic: [ipcdn] Last Call: 'Cable Device Management Information Base
	forData-Over-Cable Service Interface Specification
	CompliantCableModem s and Cable Modem Termination Systems' to
	ProposedStandard 
Thread-Index: AcYGVijuijh7uwbkQoyThfZ2WaZyzgAEMNiQAAGfVnA=
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>,
	"Brian Hedstrom" <B.Hedstrom@cablelabs.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3f2cf88677bfbdeff30feb2c80e2257d
Content-Transfer-Encoding: quoted-printable
Cc: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
	"Ipcdn \(E-mail\)" <ipcdn@ietf.org>
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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

Rich, Brian and all,

   Given where we are in the process and given the existing restrictions
in RFC2669, my first reaction would be to do a real check with operators
and implementers by asking:
	a) CM operators about their actual use of the syslog server DHCP
option in field deployments (multi-value or single?).=20
	b) CM vendors about how their implementations deal with
multi-values in the mentioned DHCP options.

   Given that syslog is UDP-based, what would it mean to have multiple
server values? It can't reliably be used for fail-over scenarios so
should mean broadcast syslog. I personally think that this would best be
done by using a management station that could act like a trap exploder
and broadcast or multicast the syslog msg to multiple servers.

Comments and feedback from the list is appreciated.
Jean-Francois

> -----Original Message-----
> From: Richard Woundy @ Comcast
> Sent: Wednesday, December 21, 2005 1:01 PM
> To: Brian Hedstrom; Wijnen, Bert (Bert)
> Cc: Ipcdn (E-mail); Richard Woundy @ Comcast
> Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information
> Base forData-Over-Cable Service Interface Specification
> CompliantCableModem s and Cable Modem Termination Systems' to
> ProposedStandard
>=20
> Brian, Bert,
>=20
> I need some help from the IPCDN working group to resolve this Last
> Call
> objection.
>=20
> The latest DOCSIS RFI specification,
> <http://www.cablemodem.com/downloads/specs/CM-SP-RFI2.0-I10-
> 051209.pdf>,
> annex D.1.1, specifies the use of five standard DHCP options:
>=20
> * Option code 1 (Subnet Mask)
> * Option code 2 (Time Offset)
> * Option code 3 (Router Option)
> * Option code 4 (Time Server Option)
> * Option code 7 (Log Server Option)
>=20
> Looking at RFC 2132,
<http://www.ietf.org/rfc/rfc2132.txt?number=3D2132>,
> it becomes obvious that DHCP options 1 and 2 are single-valued
options,
> and DHCP options 3, 4 and 7 are potentially multi-valued options.
>=20
> So it would seem that if we are worried about multi-valued DHCP
> options,
> we should be just as concerned about multiple time servers (e.g.
> docsDevServerTimeAddress) as about multiple SYSLOG servers (e.g.
> docsDevEvSyslogAddress).
>=20
> RFC 2669 (the original Cable Device MIB) was published August 1999,
> and
> RFC 2132 was published March 1997. So the MIB module restrictions for
> a
> single time server and SYSLOG server has been around for over six
> years,
> without an objection until now. Is this a real problem, or a
> theoretical
> problem?
>=20
> I can think of three reactions to this objection: (1) no changes, (2)
> clarify the relevant MIB objects so that they report the *first* DHCP
> option value if the DHCP option is multi-valued, or (3) change the MIB
> module to add tables to capture (multiple) Time Servers and/or SYSLOG
> servers.
>=20
> -- Rich
>=20
> -----Original Message-----
> From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf
> Of Wijnen, Bert (Bert)
> Sent: Wednesday, December 21, 2005 12:39 PM
> To: Ipcdn (E-mail)
> Cc: Brian Hedstrom
> Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information
> Base for Data-Over-Cable Service Interface Specification Compliant
> CableModem s and Cable Modem Termination Systems' to Proposed Standard
>=20
>=20
> Authors/Editors and WG,
>=20
> A comment on IETF Last Call for your consideration and
> possible action.
>=20
> Not sure that Brian is subscribed to IPCDN list, so pls DO
> copy him on any responses.
>=20
> Bert
>=20
>=20
>=20
> > -----Original Message-----
> > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf
> Of
>=20
> > Brian Hedstrom
> > Sent: Monday, December 19, 2005 20:23
> > To: iesg@ietf.org
> > Subject: RE: [ipcdn] Last Call: 'Cable Device Management Information
> > Base for Data-Over-Cable Service Interface Specification Compliant
> > Cable Modems and Cable Modem Termination Systems' to Proposed
> Standard
> >
> >
> > IETF:
> >
> > Regarding this object:
> >    docsDevEvSyslogAddress OBJECT-TYPE
> >            SYNTAX      InetAddress
> >            MAX-ACCESS  read-write
> >            STATUS      current
> >            DESCRIPTION
> >                "The internet address of the Syslog server.  If the
> >                 address of the server is set to any of the zero
> length
> >                 string, the 0.0.0.0 V4 address or the 0: V6 address,
> >                 syslog transmission is inhibited.  By default at
> agent
> >                 boot, this object returns the zero length string."
> >            ::=3D { docsDevEvent 10 }
> >
> > This object does not support provisioning multiple Syslog
> > servers within
> > the CM.  However, DHCP Option 7 (log server option, as
> > defined in DOCSIS
> > 2.0 Radio Frequency Interface Specification
> > [CM-SP-RFIv2.0-I09-050812])
> > does allow for specification of multiple log server addresses so
> > although they cannot all be instrumented it is possible to provide
> the
> > CM with multiple log server addresses. It seems reasonable to
> > extend the
> > docsDevEvSyslogAddress object to support multiple IP
> > addresses but I do
> > not know if this was already addressed and rejected during the
> > development of this Internet draft. The change could potentially
> mean
> > deprecating docsDevEvSyslogAddress and replacing it with a
> > table object
> > which supports Row Creation or statically creates n-number of rows.
> A
> > similar approach was taken in CableHome with the definition of
> > cabhCdpWanDnsServerTable (CABH-CDP-MIB). The structure of
> > cabhCdpWanDnsServerTable identifies an order of preference (primary,
> > secondary, or tertiary) for each entry.  See below:
> > cabhCdpWanDnsServerTable OBJECT-TYPE
> >     SYNTAX SEQUENCE OF CabhCdpWanDnsServerEntry
> >     MAX-ACCESS not-accessible
> >     STATUS current
> >     DESCRIPTION
> >             "This table contains the IP addresses of cable network
> and
> >             Internet DNS servers, in the order of preference in
> which
> >             the PS's CNP will query them, when it cannot resolve a
> DNS
> >             query using local information. Entries in this table are
> >             updated with the information contained in DHCP Option 6,
> >             received during both the WAN-Man and WAN-Data IP
> >             acquisition processes."
> >     ::=3D { cabhCdpAddr 3 }
> >
> > cabhCdpWanDnsServerEntry OBJECT-TYPE
> >     SYNTAX      CabhCdpWanDnsServerEntry
> >     MAX-ACCESS  not-accessible
> >     STATUS     current
> >     DESCRIPTION
> >             "List of cable network and Internet DNS servers."
> >     INDEX { cabhCdpWanDnsServerOrder }
> >     ::=3D { cabhCdpWanDnsServerTable 1 }
> >
> > CabhCdpWanDnsServerEntry ::=3D SEQUENCE {
> >     cabhCdpWanDnsServerOrder  INTEGER,
> >     cabhCdpWanDnsServerIpType InetAddressType,
> >     cabhCdpWanDnsServerIp     InetAddress
> >     }
> >
> > cabhCdpWanDnsServerOrder OBJECT-TYPE
> >     SYNTAX      INTEGER {
> >                     primary(1),
> >                     secondary(2),
> >                     tertiary(3)
> >                 }
> >     MAX-ACCESS  not-accessible
> >     STATUS      current
> >     DESCRIPTION
> >             "The order of preference for cable network and
> > Internet DNS
> >             servers, as listed in DHCP option 6 (Domain Server). Any
> >             time the CDC receives valid IP address information
> within
> >             DHCP Option 6, as part of lease acquisition or renewal
> of
> >             a WAN-Man or WAN-Data IP, it must update this
> information
> >             into this table.  As entries in DHCP Option 6 are
> > listed in
> >             order of preference, the highest priority entry in DHCP
> >             Option 6 must correspond to the row with a
> >             cabhCdpWanDnsServerOrder with a value of 1. If DHCP
> >             Option 6 contains 1 valid IP address, the PS MUST update
> >             the row with a cabhCdpWanDnsServerOrder value of 1 and
> >             MUST NOT modify rows with
> >             cabhCdpWanDnsServerOrder values of 2 & 3
> >             (if they exist). If DHCP Option 6 contains 2 valid
> >             IP addresses, the PS MUST update the rows with
> >             cabhCdpWanDnsServerOrder values of 1 and 2
> >             and MUST NOT modify the row with
> cabhCdpWanDnsServerOrder
> >             value of 3 (if it exists). If DHCP Option 6 contains 3
> >             valid IP addresses, the PS MUST update rows with
> >             cabhCdpWanDnsServerOrder values of 1, 2, and 3.
> >             Any DNS server information included in DHCP Option 6
> >             beyond primary, secondary and tertiary will not be
> >             represented in this table."
> >     ::=3D { cabhCdpWanDnsServerEntry 1 }
> >
> > cabhCdpWanDnsServerIpType OBJECT-TYPE
> >     SYNTAX      InetAddressType
> >     MAX-ACCESS read-only
> >     STATUS current
> >     DESCRIPTION
> >             "This parameter indicates the IP address type of a
> >             WAN DNS server."
> >     DEFVAL { ipv4 }
> >     ::=3D { cabhCdpWanDnsServerEntry 2 }
> >
> > cabhCdpWanDnsServerIp OBJECT-TYPE
> >     SYNTAX      InetAddress
> >     MAX-ACCESS  read-only
> >     STATUS      current
> >     DESCRIPTION
> >             "This parameter indicates the IP address of a WAN DNS
> >             server. The type of this address is specified by
> >             cabhCdpWanDnsServerIpType."
> >     ::=3D { cabhCdpWanDnsServerEntry 3 }
> >
> > Thanks,
> > Brian Hedstrom
> > Senior Engineer, Operation Support Systems
> > Broadband Access
> > CableLabs, Inc.
> > 858 Coal Creek Circle
> > Louisville, CO 80027
> > Direct: 303.661.3829
> > eFax: 303.664.8120
> > b.hedstrom@cablelabs.com
> >
> >
> > -----Original Message-----
> > From: The IESG [mailto:iesg-secretary@ietf.org]
> > Sent: Wednesday, December 14, 2005 9:44 AM
> > To: IETF-Announce
> > Cc: ipcdn@ietf.org
> > Subject: [ipcdn] Last Call: 'Cable Device Management Information
> Base
> > for Data-Over-Cable Service Interface Specification Compliant Cable
> > Modems and Cable Modem Termination Systems' to Proposed Standard
> >
> > The IESG has received a request from the IP over Cable Data Network
> WG
>=20
> > to consider the following document:
> >
> > - 'Cable Device Management Information Base for
> > Data-Over-Cable Service
> >    Interface Specification Compliant Cable Modems and Cable Modem
> > Termination
> >    Systems '
> >    <draft-ietf-ipcdn-device-mibv2-10.txt> as a Proposed Standard
> >
> > This document obsoletes RFC2669.
> >
> > The IESG plans to make a decision in the next few weeks, and
> solicits
> > final comments on this action.  Please send any comments to the
> > iesg@ietf.org or ietf@ietf.org mailing lists by 2005-12-28.
> >
> > The file can be obtained via
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mi
> bv2-10.txt
>=20
>=20
> _______________________________________________
> IPCDN mailing list
> IPCDN@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipcdn
>=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



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



From ipcdn-bounces@ietf.org Thu Dec 22 14:36:20 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpWEd-00029w-TT; Thu, 22 Dec 2005 14:36:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpWEb-00029Z-HZ
	for ipcdn@megatron.ietf.org; Thu, 22 Dec 2005 14:36:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23786
	for <ipcdn@ietf.org>; Thu, 22 Dec 2005 14:35:12 -0500 (EST)
Received: from mms1.broadcom.com ([216.31.210.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpWHT-0006wY-9X
	for ipcdn@ietf.org; Thu, 22 Dec 2005 14:39:16 -0500
Received: from 10.10.64.154 by mms1.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.0)); Thu, 22 Dec 2005 11:35:52 -0800
X-Server-Uuid: F962EFE0-448C-40EE-8100-87DF498ED0EA
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id 0091467420; Thu, 22
	Dec 2005 11:35:51 -0800 (PST)
Received: from mail-sj1-12.sj.broadcom.com (mail-sj1-12.sj.broadcom.com
	[10.16.128.215]) by mail-irva-8.broadcom.com (MOS 3.5.6-GR) with ESMTP
	id CKG14440; Thu, 22 Dec 2005 11:35:51 -0800 (PST)
Received: from NT-SJCA-0751.brcm.ad.broadcom.com (nt-sjca-0751
	[10.16.192.221]) by mail-sj1-12.sj.broadcom.com (Postfix) with ESMTP id
	A91DE20504; Thu, 22 Dec 2005 11:35:50 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 Dec 2005 11:35:39 -0800
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F48564396859@NT-SJCA-0751.brcm.ad.broadcom.com>
Thread-Topic: IETF I-D submission: IPCDN MTA draft09
	draft-ietf-ipcdn-pktc-mtamib-09.txt
Thread-Index: AcOJNhtSqbMYkEWKT1Wj0cQNPvF8owCK8+KAS8v7KKARYpftkDYZVcNACQvd/1ACcunnUAArCF4g
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: ipcdn@ietf.org
X-TMWD-Spam-Summary: SEV=1.1; DFV=A2005122207; IFV=2.0.6,4.0-7; RPD=4.00.0004;
	RPDID=303030312E30413031303230342E34334141464642322E303030312D452D5046786C33494E497A33445631553653544639524F673D3D;
	ENG=IBF; TS=20051222193552; CAT=NONE; CON=NONE;
X-MMS-Spam-Filter-ID: A2005122207_4.00.0004_2.0.6,4.0-7
X-WSS-ID: 6FB5DF923XG799835-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
Subject: [ipcdn] RE: IETF I-D submission: IPCDN MTA draft09
 draft-ietf-ipcdn-pktc-mtamib-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>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org


All,

The following comments are addressed in the newly released MTA MIB
draft-09:

1. http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01832.html :

	i. New subsection 3.7 is introduced which contains lacking
citation of [RFC3629] along with explanation of the issues related to
the UTF8String encoding differences in RFC 2279 and RFC 3629.

	ii. New reference added to Section 7 "Informative References"
(with added citation in section 3.7):

   [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
             RFC 2279, January 1998.=20

2. http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01836.html :

	i. New subsection 3.7 includes the new text proposed in the
comment.=20
	ii. The same text is added into the complience statements for
the pktcMtaDevRealmOrgName Object.

Eugene.

-----Original Message-----
From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]=20
Sent: Wednesday, December 21, 2005 2:23 PM
To: internet-drafts@ietf.org
Cc: Richard Woundy @ Comcast; Eugene Nechamkin; bwijnen@lucent.com
Subject: IETF I-D submission: IPCDN MTA draft09
draft-ietf-ipcdn-pktc-mtamib-09.txt

Please find attached an update to an existing IPCDN wg I-D.

Title: Multimedia Terminal Adapter (MTA) Management Information Base
               for PacketCable and IPCablecom compliant device
=20
Author(s)	: Eugene Nechamkin, Jean-Francois Mule
=20
Filename	: draft-ietf-ipcdn-pktc-mtamib-09.txt
=20
Working Group: IPCDN


Thanks,
Jean-Francois Mule.
jfm@cablelabs.com
IPCDN co-chair.




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



From ipcdn-bounces@ietf.org Tue Dec 27 18:50:48 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ErOae-0003AC-JM; Tue, 27 Dec 2005 18:50:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ErOZy-000316-4M; Tue, 27 Dec 2005 18:50:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07066;
	Tue, 27 Dec 2005 18:48:54 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ErOdq-0001nn-P1; Tue, 27 Dec 2005 18:54:07 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ErOZt-0003RN-UE; Tue, 27 Dec 2005 18:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ErOZt-0003RN-UE@newodin.ietf.org>
Date: Tue, 27 Dec 2005 18:50:01 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipcdn@ietf.org
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-pktc-mtamib-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>
Sender: ipcdn-bounces@ietf.org
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		: 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-09.txt
	Pages		: 61
	Date		: 2005-12-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-mtamib-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-mtamib-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-mtamib-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: <2005-12-27174021.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2005-12-27174021.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--




