From ipcdn-bounces@ietf.org Mon Jan 02 07:48:08 2006
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 1EtP6e-0005Yw-E0; Mon, 02 Jan 2006 07:48:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EtP6d-0005Yc-9Z
	for ipcdn@megatron.ietf.org; Mon, 02 Jan 2006 07:48: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 HAA24400
	for <ipcdn@ietf.org>; Mon, 2 Jan 2006 07:46:54 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtPBh-0007BE-5B
	for ipcdn@ietf.org; Mon, 02 Jan 2006 07:53:22 -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 k02Clure018892; 
	Mon, 2 Jan 2006 06:47:57 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BR8Z2F>; Mon, 2 Jan 2006 13:47:55 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508F17F29@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Russ Housley (E-mail)" <housley@vigilsec.com>
Date: Mon, 2 Jan 2006 13:47:55 +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: d6b246023072368de71562c0ab503126
Cc: "Ipcdn \(E-mail\)" <ipcdn@ietf.org>
Subject: [ipcdn] FW: COMMENT: draft-ietf-imss-fc-fam-mib-03.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

Sharp eyes Russ!
I have "fixed" it with a note to RFC-Editor.

Bert

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of
Russ Housley
Sent: Monday, January 02, 2006 00:00
To: iesg@ietf.org
Subject: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt


Fibre Channel Fabric Address Manager MIB (Proposed Standard)

COMMENT

   Section 12: s/t11FamRcFabricNotifyEnabl/t11FamRcFabricNotifyEnable/


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



From ipcdn-bounces@ietf.org Tue Jan 10 23:03:02 2006
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 1EwXCQ-0007ol-Fu; Tue, 10 Jan 2006 23:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwXCO-0007oa-Gw
	for ipcdn@megatron.ietf.org; Tue, 10 Jan 2006 23:03: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 XAA08871
	for <ipcdn@ietf.org>; Tue, 10 Jan 2006 23:01:41 -0500 (EST)
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwXJE-0004Jk-5h
	for ipcdn@ietf.org; Tue, 10 Jan 2006 23:10:04 -0500
Received: from ([10.20.9.174])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.16119153;
	Tue, 10 Jan 2006 23:02:39 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 10 Jan 2006 23:02:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Jan 2006 23:02:38 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF53C@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: PROTO preparation for IPCDN MTA MIB
	draft-ietf-ipcdn-pktc-mtamib-09.txt
Thread-Index: AcOJNhtSqbMYkEWKT1Wj0cQNPvF8owCK8+KAS8v7KKARYpftkDYZVcNACQvd/1ACcunnUAArCF4gA8NHMyA=
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Eugene Nechamkin" <enechamkin@broadcom.com>,
	"Jean-Francois Mule" <jf.mule@cablelabs.com>
X-OriginalArrivalTime: 11 Jan 2006 04:02:39.0515 (UTC)
	FILETIME=[DD306EB0:01C61663]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: quoted-printable
Cc: ipcdn@ietf.org
Subject: [ipcdn] PROTO preparation for IPCDN MTA MIB
	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

Jean-Fran=E7ois, Eugene, and members of the IPCDN working group,

At the November IETF meeting in Vancouver, we discussed modifications to =
the PacketCable/IPCableCom MTA MIB version -07; the recommended changes =
were incorporated in version -08. Version -08 prompted a comment from =
Bert Wijnen about a missing citation for RFC3629, and a comment from =
Randy Presuhn about UTF-8 encoding in RFC2279 vs. RFC3629 (six octet =
encoding maximum versus four octet encoding maximum). These comments =
prompted modifications that are incorporated in version -09.

I understand that version -09 of the draft is considered complete, so I =
am working on the PROTO write-up. The PROTO process is defined in =
draft-ietf-proto-wgchair-doc-shepherding-05.txt.

There are a couple of questions we need to answer as a WG. See below my =
proposed responses which I think represent the WG status.  If my =
responses are not representative of the WG consensus or incorrect, or if =
you have any comments, questions or concerns, please let me know by =
Friday January 13 2006.

This is for: =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-09.txt

   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?

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.

   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.)?

No.

   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?

This document represents the WG consensus as a whole; the WG as a whole =
understands and agrees with it.

   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.

If anyone would appeal - please let me know =
(richard_woundy@cable.comcast.com). Otherwise I assume that no one has =
threatened an appeal.

Richard Woundy
PROTO shepherd for draft-ietf-ipcdn-pktc-mtamib-09.txt

-----Original Message-----
From: Eugene Nechamkin [mailto:enechamkin@broadcom.com]=20
Sent: Thursday, December 22, 2005 2:36 PM
To: ipcdn@ietf.org
Cc: Jean-Francois Mule; Woundy, Richard
Subject: RE: IETF I-D submission: IPCDN MTA draft09 =
draft-ietf-ipcdn-pktc-mtamib-09.txt



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 Jan 10 23:03:02 2006
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 1EwXCQ-0007pD-Rg; Tue, 10 Jan 2006 23:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwXCP-0007of-Vt
	for ipcdn@megatron.ietf.org; Tue, 10 Jan 2006 23:03:02 -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 XAA08874
	for <ipcdn@ietf.org>; Tue, 10 Jan 2006 23:01:41 -0500 (EST)
Received: from pacdcoavas09.cable.comcast.com ([208.17.33.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwXJE-0004Jm-Pm
	for ipcdn@ietf.org; Tue, 10 Jan 2006 23:10:05 -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
Date: Tue, 10 Jan 2006 23:02:38 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF53D@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: PROTO preparation for DOCSIS RFIv2 MIB
	draft-ietf-ipcdn-docs-rfmibv2-14.txt
Thread-Index: AcYWYo6KqWd4d+a1Q76H+PnXj1vLYA==
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Eduardo Cardona" <e.cardona@CableLabs.com>
X-OriginalArrivalTime: 11 Jan 2006 04:02:39.0843 (UTC)
	FILETIME=[DD627B30:01C61663]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
Cc: "Ipcdn \(E-mail\)" <ipcdn@ietf.org>
Subject: [ipcdn] PROTO preparation for DOCSIS RFIv2 MIB
	draft-ietf-ipcdn-docs-rfmibv2-14.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

Eduardo and members of the IPCDN working group,

Prior to the November IETF meeting in Vancouver, Eduardo Cardona
produced version -14 of the DOCSIS RFIv2 MIB, in response to comments
from the AD review by Bert Wijnen. There were no further technical
comments at the IETF meeting or on the IPCDN mailing list.

I understand that version -14 of the draft is considered complete, so I
am working on the PROTO write-up. The PROTO process is defined in
draft-ietf-proto-wgchair-doc-shepherding-05.txt.

There are a couple of questions we need to answer as a WG. See below my
proposed responses which I think represent the WG status.  If my
responses are not representative of the WG consensus or incorrect, or if
you have any comments, questions or concerns, please let me know by
Friday January 13 2006.

This is for:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt

   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?

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.

   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.)?

No.

   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?

This document represents the WG consensus as a whole; the WG as a whole
understands and agrees with it.

   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.

If anyone would appeal - please let me know
(richard_woundy@cable.comcast.com). Otherwise I assume that no one has
threatened an appeal.

Richard Woundy
PROTO shepherd for draft-ietf-ipcdn-docs-rfmibv2-14.txt

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



From ipcdn-bounces@ietf.org Wed Jan 11 17:30:03 2006
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 1EwoTj-00049Z-AO; Wed, 11 Jan 2006 17:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwoTi-000499-Fi
	for ipcdn@megatron.ietf.org; Wed, 11 Jan 2006 17:30:02 -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 RAA20082
	for <ipcdn@ietf.org>; Wed, 11 Jan 2006 17:28:42 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ewoae-0002Tp-SJ
	for ipcdn@ietf.org; Wed, 11 Jan 2006 17:37:16 -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 k0BMTdLm017804;
	Wed, 11 Jan 2006 15:29:40 -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: Wed, 11 Jan 2006 15:29:39 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804012CE443@srvxchg.cablelabs.com>
Thread-Topic: PROTO preparation for IPCDN MTA MIB
	draft-ietf-ipcdn-pktc-mtamib-09.txt
Thread-Index: AcOJNhtSqbMYkEWKT1Wj0cQNPvF8owCK8+KAS8v7KKARYpftkDYZVcNACQvd/1ACcunnUAArCF4gA8NHMyAAMhi2UA==
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Cc: ipcdn@ietf.org, Eugene Nechamkin <enechamkin@broadcom.com>
Subject: [ipcdn] RE: PROTO preparation for IPCDN MTA MIB
	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

Rich,

   Thanks for the proto write-up. It reflects my understanding of the ID =
status as a co-author.

Jean-Fran=E7ois

> -----Original Message-----
> From: Richard Woundy @ Comcast
> Sent: Tuesday, January 10, 2006 9:03 PM
> To: Eugene Nechamkin; Jean-Francois Mule
> Cc: ipcdn@ietf.org
> Subject: PROTO preparation for IPCDN MTA MIB draft-ietf-ipcdn-pktc-
> mtamib-09.txt
>=20
> Jean-Fran=E7ois, Eugene, and members of the IPCDN working group,
>=20
> At the November IETF meeting in Vancouver, we discussed modifications
> to the PacketCable/IPCableCom MTA MIB version -07; the recommended
> changes were incorporated in version -08. Version -08 prompted a
> comment from Bert Wijnen about a missing citation for RFC3629, and a
> comment from Randy Presuhn about UTF-8 encoding in RFC2279 vs. RFC3629
> (six octet encoding maximum versus four octet encoding maximum). These
> comments prompted modifications that are incorporated in version -09.
>=20
> I understand that version -09 of the draft is considered complete, so
> I am working on the PROTO write-up. The PROTO process is defined in
> draft-ietf-proto-wgchair-doc-shepherding-05.txt.
>=20
> There are a couple of questions we need to answer as a WG. See below
> my proposed responses which I think represent the WG status.  If my
> responses are not representative of the WG consensus or incorrect, or
> if you have any comments, questions or concerns, please let me know by
> Friday January 13 2006.
>=20
> This is for: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-
> mtamib-09.txt
>=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
>    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.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
> If anyone would appeal - please let me know
> (richard_woundy@cable.comcast.com). Otherwise I assume that no one has
> threatened an appeal.
>=20
> Richard Woundy
> PROTO shepherd for draft-ietf-ipcdn-pktc-mtamib-09.txt


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



From ipcdn-bounces@ietf.org Wed Jan 11 19:48:20 2006
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 1EwqdY-0003wb-92; Wed, 11 Jan 2006 19:48:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwqdW-0003wV-LC
	for ipcdn@megatron.ietf.org; Wed, 11 Jan 2006 19:48:18 -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 TAA01048
	for <ipcdn@ietf.org>; Wed, 11 Jan 2006 19:46:57 -0500 (EST)
Received: from mms1.broadcom.com ([216.31.210.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwqkU-0007Ku-3a
	for ipcdn@ietf.org; Wed, 11 Jan 2006 19:55:33 -0500
Received: from 10.10.64.154 by mms1.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.2.0)); Wed, 11 Jan 2006 16:47:57 -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 6651167420; Wed, 11
	Jan 2006 16:47:57 -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 CQU59357; Wed, 11 Jan 2006 16:45:52 -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
	D219E20502; Wed, 11 Jan 2006 16:45:51 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 11 Jan 2006 16:45:49 -0800
Message-ID: <9C5C578DD43AFD4EA7A9F0BDB2F4856452BFC9@NT-SJCA-0751.brcm.ad.broadcom.com>
Thread-Topic: PROTO preparation for IPCDN MTA MIB
	draft-ietf-ipcdn-pktc-mtamib-09.txt
Thread-Index: AcOJNhtSqbMYkEWKT1Wj0cQNPvF8owCK8+KAS8v7KKARYpftkDYZVcNACQvd/1ACcunnUAArCF4gA8NHMyAAMhi2UAAElItA
From: "Eugene Nechamkin" <enechamkin@broadcom.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>,
	"Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
X-TMWD-Spam-Summary: SEV=1.1; DFV=A2006011109; IFV=2.0.6,4.0-7; RPD=4.00.0004;
	RPDID=303030312E30413031303230322E34334335413634312E303031342D412D;
	ENG=IBF; TS=20060112004800; CAT=NONE; CON=NONE;
X-MMS-Spam-Filter-ID: A2006011109_4.00.0004_2.0.6,4.0-7
X-WSS-ID: 6FDB78B73V02699741-01-01
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
Cc: ipcdn@ietf.org
Subject: [ipcdn] RE: PROTO preparation for IPCDN MTA MIB
 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


Rich,

I agree with the write up, it adequately reflects my understanding of =
the current status of the draft.=20

Regards,

Eugene.

-----Original Message-----
From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]=20
Sent: Wednesday, January 11, 2006 2:30 PM
To: Richard Woundy @ Comcast
Cc: ipcdn@ietf.org; Eugene Nechamkin
Subject: RE: PROTO preparation for IPCDN MTA MIB =
draft-ietf-ipcdn-pktc-mtamib-09.txt

Rich,

   Thanks for the proto write-up. It reflects my understanding of the ID =
status as a co-author.

Jean-Fran=E7ois

> -----Original Message-----
> From: Richard Woundy @ Comcast
> Sent: Tuesday, January 10, 2006 9:03 PM
> To: Eugene Nechamkin; Jean-Francois Mule
> Cc: ipcdn@ietf.org
> Subject: PROTO preparation for IPCDN MTA MIB draft-ietf-ipcdn-pktc-=20
> mtamib-09.txt
>=20
> Jean-Fran=E7ois, Eugene, and members of the IPCDN working group,
>=20
> At the November IETF meeting in Vancouver, we discussed modifications=20
> to the PacketCable/IPCableCom MTA MIB version -07; the recommended=20
> changes were incorporated in version -08. Version -08 prompted a=20
> comment from Bert Wijnen about a missing citation for RFC3629, and a=20
> comment from Randy Presuhn about UTF-8 encoding in RFC2279 vs. RFC3629 =

> (six octet encoding maximum versus four octet encoding maximum). These =

> comments prompted modifications that are incorporated in version -09.
>=20
> I understand that version -09 of the draft is considered complete, so=20
> I am working on the PROTO write-up. The PROTO process is defined in=20
> draft-ietf-proto-wgchair-doc-shepherding-05.txt.
>=20
> There are a couple of questions we need to answer as a WG. See below=20
> my proposed responses which I think represent the WG status.  If my=20
> responses are not representative of the WG consensus or incorrect, or=20
> if you have any comments, questions or concerns, please let me know by =

> Friday January 13 2006.
>=20
> This is for: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-
> mtamib-09.txt
>=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=20
> MIB doctors who provided valuable comments to improve the quality of=20
> the MIB module.
>=20
>    1.c) Do you have concerns that the document needs more review from=20
> a
>         particular (broader) perspective (e.g., security, operational
>         complexity, someone familiar with AAA, etc.)?
>=20
> No.
>=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=20
> 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
> If anyone would appeal - please let me know=20
> (richard_woundy@cable.comcast.com). Otherwise I assume that no one has =

> threatened an appeal.
>=20
> Richard Woundy
> PROTO shepherd for draft-ietf-ipcdn-pktc-mtamib-09.txt




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



From ipcdn-bounces@ietf.org Mon Jan 16 19:13:27 2006
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 1EyeTX-0004Dp-6D; Mon, 16 Jan 2006 19:13:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyeTV-0004BB-65
	for ipcdn@megatron.ietf.org; Mon, 16 Jan 2006 19:13:25 -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 TAA27314
	for <ipcdn@ietf.org>; Mon, 16 Jan 2006 19:12:00 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyebW-0002X6-JM
	for ipcdn@ietf.org; Mon, 16 Jan 2006 19:21:42 -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 k0H0D620028223;
	Mon, 16 Jan 2006 17:13:06 -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
Date: Mon, 16 Jan 2006 17:13:06 -0700
Message-ID: <5259D0D7419C6149B347837A2E64F46F014957CA@srvxchg.cablelabs.com>
Thread-Topic: PROTO preparation for DOCSIS RFIv2 MIB
	draft-ietf-ipcdn-docs-rfmibv2-14.txt
Thread-Index: AcYWYo6KqWd4d+a1Q76H+PnXj1vLYAEl/TDw
From: "Eduardo Cardona" <e.cardona@CableLabs.com>
To: "Richard Woundy @ Comcast" <Richard_woundy@cable.comcast.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
Cc: "Ipcdn \(E-mail\)" <ipcdn@ietf.org>
Subject: [ipcdn] RE: PROTO preparation for DOCSIS RFIv2 MIB
	draft-ietf-ipcdn-docs-rfmibv2-14.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

Thanks Rick for preparing the PROTO write up

The answers to the questions reflect my understanding of the current
status of the ID

Thanks

Eduardo
-----Original Message-----
From: Richard Woundy @ Comcast=20
Sent: Tuesday, January 10, 2006 9:03 PM
To: Eduardo Cardona
Cc: Ipcdn (E-mail)
Subject: PROTO preparation for DOCSIS RFIv2 MIB
draft-ietf-ipcdn-docs-rfmibv2-14.txt

Eduardo and members of the IPCDN working group,

Prior to the November IETF meeting in Vancouver, Eduardo Cardona
produced version -14 of the DOCSIS RFIv2 MIB, in response to comments
from the AD review by Bert Wijnen. There were no further technical
comments at the IETF meeting or on the IPCDN mailing list.

I understand that version -14 of the draft is considered complete, so I
am working on the PROTO write-up. The PROTO process is defined in
draft-ietf-proto-wgchair-doc-shepherding-05.txt.

There are a couple of questions we need to answer as a WG. See below my
proposed responses which I think represent the WG status.  If my
responses are not representative of the WG consensus or incorrect, or if
you have any comments, questions or concerns, please let me know by
Friday January 13 2006.

This is for:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt

   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?

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.

   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.)?

No.

   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?

This document represents the WG consensus as a whole; the WG as a whole
understands and agrees with it.

   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.

If anyone would appeal - please let me know
(richard_woundy@cable.comcast.com). Otherwise I assume that no one has
threatened an appeal.

Richard Woundy
PROTO shepherd for draft-ietf-ipcdn-docs-rfmibv2-14.txt



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



From ipcdn-bounces@ietf.org Mon Jan 23 00:58:41 2006
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 1F0uiv-0006XQ-Km; Mon, 23 Jan 2006 00:58:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0uis-0006Uu-PQ
	for ipcdn@megatron.ietf.org; Mon, 23 Jan 2006 00:58:40 -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 AAA18703
	for <ipcdn@ietf.org>; Mon, 23 Jan 2006 00:57:09 -0500 (EST)
Received: from web36111.mail.mud.yahoo.com ([66.163.179.225])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F0us8-0001A0-JK
	for ipcdn@ietf.org; Mon, 23 Jan 2006 01:08:15 -0500
Received: (qmail 49235 invoked by uid 60001); 23 Jan 2006 05:58:26 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=eLUaKnFGdLX2To+9YeoMb8BI4RXY9x70L26LvPkqJCq1BrUIOWpGpY6p+Zj2QO4bi2BCjTwqn0YAyc2iqNAgqXnLYWV0XL/iV7n/B6nXBNmbYTh5oXwVAgxtiP9WK9u0NGRQNiIl2oOgdFlpzLHZjsb1s/ky2r0avBIG7YRndIE=
	; 
Message-ID: <20060123055826.49233.qmail@web36111.mail.mud.yahoo.com>
Received: from [216.211.71.34] by web36111.mail.mud.yahoo.com via HTTP;
	Sun, 22 Jan 2006 21:58:26 PST
Date: Sun, 22 Jan 2006 21:58:26 -0800 (PST)
From: Hassan Naser <hnaser_ca@yahoo.com>
To: ipcdn@ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Subject: [ipcdn] CFP: Special Session on Broadband Access Networks
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="===============0428084619=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

--===============0428084619==
Content-Type: multipart/alternative; boundary="0-65087601-1137995906=:48256"
Content-Transfer-Encoding: 8bit

--0-65087601-1137995906=:48256
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


(Apologies if you receive multiple copies of this CFP)

 
  C A L L   F O R   P A P E R S 
  =============================
   
  The 2006 International Conference on 
  Communications in Computing (CIC'06)
   
  June 26-29, 2006
  Monte Carlo Resort, Las Vegas, Nevada, USA
   
   
  The CIC'06 Conference will be held simultaneously with a number of other international conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). For the complete list of joint conferences refer to: http://www.world-academy-of-science.org/worldcomp06/ws )
   
   
  SPECIAL SESSION: Broadband Optical Access Networks
   
   
  SCOPE OF THE SESSION
   
  Passive Optical Network (PON) technology is one of the most promising fiber-based access solutions that can deliver high-speed services to residential, enterprise, and business customers. This session is an opportunity for academia, industry, and researchers to discuss latest advances in the design, architecture, analysis, simulation, and performance evaluation of broadband optical access networks. Particular emphasis will be made on PON technology. Possible topics of interest covered in this session include, but are not limited to:
   
  - Architectures and protocols for PON, including, EPON, GPON, APON
  - Dynamic bandwidth allocation 
  - Quality of Service (QoS) 
  - Survivability mechanisms for PON 
  - Medium access control
  - Network management and control
  - Modeling and simulation of PON
  - Other optical access technologies, including, FTTH, FTTC, FTTB
   
   
  SUBMISSION OF PAPERS:
   
  Prospective authors are invited to submit their draft paper (about 5 to 8 pages - single space, font size of 10 to 12) via email to Dr. Hassan Naser (hnaser@lakeheadu.ca) by Feb. 20, 2006. E-mail submissions in MS document or PDF formats are preferable (Fax or postal submissions are also fine.)  All reasonable typesetting formats are acceptable (later, the authors of accepted papers will be asked to follow a particular typesetting format to prepare their papers for publication.)


  The length of the Camera-Ready papers (if accepted) will be limited to 7 (IEEE style) pages. Papers must not have been previously published or currently submitted for publication elsewhere. The first page of the draft paper should include: title of the paper, name, affiliation, postal address, E-mail address, telephone number, and Fax number for each author. The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Also, the name of the conference that the paper is being submitted to must be mentioned on the first page.


  Papers will be evaluated for originality, significance, clarity, and soundness.  Each paper will be refereed by two researchers in the topical area.  The Camera-Ready papers will be reviewed by the session chair.
  


  CATEGORIES OF ACCEPTED PAPERS:


  (RRP)  Regular Research Papers
          7-page IEEE-style publication in the proceedings
          20-minute formal presentation slot
   
  (RRR)  Regular Research Reports
          7-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
   
  (SRP)  Short Research Papers
          4-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
   
  (PST)  Posters
          1-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
   
   
  PURPOSE / HISTORY:


  CIC'06 is an international conference held simultaneously (ie, same location and dates) with a number of other joint conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing).  WORLDCOMP'06 is the largest annual gathering of researchers in computer science, computer engineering and applied computing.  Many of the 28 joint conferences in WORLDCOMP are the premier conferences for presentation of advances in their respective fields. WORLDCOMP'06 is composed of the following international conferences: Parallel and Distributed Processing Techniques and Applications; Scientific Computing; Grid Computing and Applications; Security and Management; Artificial Intelligence; Machine Learning; Software Engineering Research and Practice; Programming Languages and Compilers; Internet Computing; Semantic Web and Web Services; Computer Design; Real-Time Computing Systems and Applications; Embedded Systems and Application!
 s;
 Wireless Networks; Pervasive Systems and Computing; Image Processing, Computer Vision, and Pattern Recognition; Computer Graphics and Virtual Reality; Modeling, Simulation and Visualization Methods; Computer Games Development; Frontiers in Education in Computer Science and Engineering; Foundations of Computer Science; e-Learning, e-Business, Enterprise Information Systems, e-Government, and Outsourcing; Data Mining; Information and Knowledge Engineering; Bioinformatics and Computational Biology; Computing in Nanotechnology; Engineering of Reconfigurable Systems and Algorithms; Communications in Computing.

The motivation is to assemble a spectrum of affiliated research conferences into a coordinated research meeting held in a common place at a common time.  The main goal is to provide a forum for exchange of ideas in a number of research areas that interact.  The model used to form these annual conferences facilitates communication among researchers in different fields of computer science, computer engineering and applied computing.  Both inward research (core areas of computer science and engineering) and outward research (multi-disciplinary, Inter-disciplinary, and applications) will be covered during the conferences. 
   
   
  LOCATION OF CONFERENCES:


  The conferences will be held in the Monte Carlo Resort hotel, Las Vegas, Nevada, USA (with any overflows at other near-by hotels). The Monte Carlo Resort is a mega hotel with excellent conference facilities and over 3,000 rooms. The hotel is minutes from the airport with 24-hour shuttle service to and from the airport. This hotel has many recreational attractions, including: waterfalls, spa, pools and kiddie pools, sunning decks, Easy River water ride, wave pool with cascades, lighted tennis courts, health spa (with workout equipment, whirlpool, sauna, ...), arcade virtual reality game rooms, nightly shows, snack bars, a number of restaurants, shopping area, bars, ...  Many of these attractions are open 24 hours a day and most are suitable for families and children. The negotiated room rate for conference attendees is very reasonable.  The hotel is within walking distance from most other attractions (major shopping areas, recreational destinations, fine dining and night cl!
 ubs, free
 street shows, ...).
   
   
  SESSION CHAIR:


  Dr. Hassan Naser
  Department of Software Engineering
  Lakehead University
  Thunder Bay, Ontario P7B 5E1 Canada
  Email: hnaser@lakeheadu.ca
  Fax: +1 (807) 766 7243
   
   
  IMPORTANT DATES: 
  
Submission of papers:                          February 20, 2006  
  Notification of acceptance:                    March 20, 2006
Submission of camera-ready papers:     April 20, 2006

		
---------------------------------
Yahoo! Photos
 Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.
--0-65087601-1137995906=:48256
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV id=RTEContent><PRE>(Apologies if you receive multiple copies of this CFP)</PRE><PRE><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p>&nbsp;</o:p></PRE>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">C A L L <SPAN style="mso-spacerun: yes">&nbsp;</SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN>F O R <SPAN style="mso-spacerun: yes">&nbsp;&nbsp;</SPAN>P A P E R S <o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">=============================<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">The 2006 International Conference on <o:p></o:p></SPAN></div>  <div class=MsoNormal
 style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">Communications in Computing (CIC'06)<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">June 26-29, 2006<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Monte Carlo Resort, <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:place w:st="on"><st1:City w:st="on">Las Vegas</st1:City>, <st1:State w:st="on">Nevada</st1:State>, <st1:country-region w:st="on">USA</st1:country-region></st1:place><SPAN style="COLOR: black"><o:p></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY:
 Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">The CIC'06 Conference will be held simultaneously with a number of other international conferences <SPAN style="COLOR: black">as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). </SPAN>For the complete list of joint conferences refer to: <A href="http://www.world-academy-of-science.org/worldcomp06/ws" target=l><SPAN style="COLOR: #3333cc">http://www.world-academy-of-science.org/worldcomp06/ws</SPAN></A> )<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><SPAN style="mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm
 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">SPECIAL SESSION: Broadband Optical Access Networks<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><SPAN style="mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">SCOPE OF THE SESSION<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Passive Optical Network (PON) techno!
 logy is
 one of the most promising fiber-based access solutions that can deliver high-speed services to residential, enterprise, and business customers. This session is an opportunity for academia, industry, and researchers to discuss <SPAN style="COLOR: black">latest advances in the design, architecture, analysis, simulation, and performance evaluation </SPAN>of <SPAN style="COLOR: black">broadband optical access networks. Particular emphasis will be made on PON technology.</SPAN> Possible topics of interest covered in this session include, but are not limited to:<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">- Architectures and protocols for <SPAN style="COLOR: black; mso-bidi-font-weight: bold">PON, including, EPON, GPON, APON<o:p></o:p></SPAN></SPAN></div>  <div class=M!
 soNormal
 style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Dynamic bandwidth allocation <SPAN style="COLOR: black; mso-bidi-font-weight: bold"><o:p></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Quality of Service (QoS) <o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana;
 mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> <SPAN style="mso-bidi-font-weight: bold">Survivability mechanisms for PON</SPAN> <o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Medium access control<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol;
 mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Network management and control<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Modeling and simulation of PON<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-ascii-font-family: Verdana; mso-hansi-font-family: Verdana; mso-char-type: symbol; mso-symbol-font-family: Symbol"><SPAN style="mso-char-type: symbol; mso-symbol-font-family: Symbol">-</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> Other optical access technologies, including, FTTH, FTTC,
 FTTB<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><SPAN style="mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">SUBMISSION OF PAPERS:</SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">Prospective authors are invited to submit their draft paper (about 5 to 8 pages - single space, font size of 10 to 12) via email to Dr. Hassan Naser (</SPAN><SPAN
 style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><A href="mailto:hnaser@lakeheadu.ca">hnaser@lakeheadu.ca</A>) <SPAN style="COLOR: black">by Feb. 20, 2006. E-mail submissions in MS document or PDF formats are preferable (Fax or postal submissions are also fine.)&nbsp; All reasonable typesetting formats are acceptable (later, the authors of accepted papers will be asked to follow a particular typesetting format to prepare their papers for publication.)<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><o:p></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">The length of the Camera-Ready papers (if accepted) will be limited to 7 (IEEE style) pages.&nbsp;Papers must not have been previously published or currently submitted for publication elsewhere.&nbsp;The first page of the draft paper should include: title of the paper, name, affiliation, postal !
 address,
 E-mail address, telephone number, and Fax number for each author.&nbsp;The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Also, the name of the conference that the paper is being submitted to must be mentioned on the first page.<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">Papers will be evaluated for originality, significance, clarity, and soundness.&nbsp; Each paper will be refereed by two researchers in the topical area.&nbsp; The Camera-Ready papers will be reviewed by </SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">the session chair<SPAN style="COLOR: black">.</SPAN><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMIL!
 Y:
 Verdana"><BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">CATEGORIES OF ACCEPTED PAPERS:<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">(RRP)&nbsp; Regular Research Papers<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7-page IEEE-style publication in the proceedings<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;20-minute formal presentation slot<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"!
 ><SPAN
 style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">(RRR)&nbsp; Regular Research Reports<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7-page IEEE-style publication in the proceedings<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Presentation in an informal setting (during Discussion Sessions)<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">(SRP)&nbsp; Short Research Papers<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4-page IEEE-style publication in the proceedings<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Presentation in an informal setting (during Discussion Sessions)<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY:
 Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">(PST)&nbsp; Posters<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1-page IEEE-style publication in the proceedings<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Presentation in an informal setting (during Discussion Sessions)<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">PURPOSE / HISTORY:<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="F!
 ONT-SIZE:
 10pt; FONT-FAMILY: Verdana">CIC'06 is an international conference held simultaneously (ie, same location and dates) with a number of other joint conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing).&nbsp; WORLDCOMP'06 is the largest annual gathering of researchers in computer science, computer engineering and applied computing.&nbsp; Many of the 28 joint conferences in WORLDCOMP are the premier conferences for presentation of advances in their respective fields. WORLDCOMP'06 is composed of the following international conferences: Parallel and Distributed Processing Techniques and Applications; Scientific Computing; Grid Computing and Applications; Security and Management; Artificial Intelligence; Machine Learning; Software Engineering Research and Practice; Programming Languages and Compilers; Internet Computing; Semantic Web and Web Services; Computer Design; Real-Time Computing Systems and Applicati!
 ons;
 Embedded Systems and Applications; Wireless Networks; Pervasive Systems and Computing; Image Processing, Computer Vision, and Pattern Recognition; Computer Graphics and Virtual Reality; Modeling, Simulation and Visualization Methods; Computer Games Development; Frontiers in Education in Computer Science and Engineering; Foundations of Computer Science; e-Learning, e-Business, Enterprise Information Systems, e-Government, and Outsourcing; Data Mining; Information and Knowledge Engineering; Bioinformatics and Computational Biology; Computing in Nanotechnology; Engineering of Reconfigurable Systems and Algorithms; Communications in Computing.<BR><BR>The motivation is to assemble a spectrum of affiliated research conferences into a coordinated research meeting held in a common place at a common time.&nbsp; The main goal is to provide a forum for exchange of ideas in a number of research areas that interact.&nbsp; The model used to form these annual conferences facilitates commu!
 nication
 among researchers in different fields of computer science, computer engineering and applied computing.&nbsp; Both inward research (core areas of computer science and engineering) and outward research (multi-disciplinary, Inter-disciplinary, and applications) will be covered during the conferences. <o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">LOCATION OF CONFERENCES:<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"></SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN
 style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">The conferences will be held in the Monte Carlo Resort hotel, <st1:place w:st="on"><st1:City w:st="on">Las Vegas</st1:City>, <st1:State w:st="on">Nevada</st1:State>, <st1:country-region w:st="on">USA</st1:country-region></st1:place> (with any overflows at other near-by hotels).&nbsp;The Monte Carlo Resort is a mega hotel with excellent conference facilities and over 3,000 rooms. The hotel is minutes from the airport with 24-hour shuttle service to and from the airport.&nbsp;This hotel has many recreational attractions, including: waterfalls, spa, pools and kiddie pools, sunning decks, Easy River water ride, wave pool with cascades, lighted tennis courts, health spa (with workout equipment, whirlpool, sauna, ...), arcade virtual reality game rooms, nightly shows, snack bars, a number of restaurants, shopping area, bars, ...&nbsp; Many of these attractions are open 24 hours a day and most are suitable for families and
 children. The negotiated room rate for conference attendees is very reasonable.&nbsp; The hotel is within walking distance from most other attractions (major shopping areas, recreational destinations, fine dining and night clubs, free street shows, ...).<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">SESSION CHAIR:<BR style="mso-special-character: line-break"><BR style="mso-special-character: line-break"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Dr. Hassan Naser<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0c!
 m 0cm
 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Department of Software Engineering<o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><st1:place w:st="on"><st1:PlaceName w:st="on"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Lakehead</SPAN></st1:PlaceName><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"> <st1:PlaceType w:st="on">University</st1:PlaceType></SPAN></st1:place><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><st1:place w:st="on"><st1:City w:st="on"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Thunder Bay</SPAN></st1:City><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">, <st1:State w:st="on">Ontario</st1:State> <st1:PostalCode w:st="on">P7B 5E1</st1:PostalCode> <st1:country-region w:st="on">Canada</st1:country-region></SPAN></st1:place><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p></o:p></SPAN></div>  <div class=MsoNormal
 style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Email: <A href="mailto:hnaser@lakeheadu.ca">hnaser@lakeheadu.ca</A><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Fax<SPAN style="TEXT-TRANSFORM: uppercase">: +1 (807) 766 7243</SPAN><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><o:p>&nbsp;</o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">IMPORTANT DATES: <o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><BR>Submission of papers:<SPAN style="mso-spacerun:
 yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>February&nbsp;20, 2006&nbsp;&nbsp;</SPAN><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-bidi-font-family: 'Courier New'"><o:p></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana">Notification of acceptance:<SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>March 20, 2006<o:p></o:p></SPAN></div><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; mso-bidi-font-family: 'Times New Roman'">Submission of camera-ready papers:<SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;
 </SPAN>April 20, 2006</SPAN></DIV><p>
		<hr size=1>Yahoo! Photos<br> 
Ring in the New Year with <a href="http://us.rd.yahoo.com/mail_us/taglines/photos/*http://pa.yahoo.com/*http://us.rd.yahoo.com/mail_us/taglines/photos/evt=38087/*http://pg.photos.yahoo.com/ph//page?.file=calendar_splash.html&.dir=">Photo Calendars</a>. Add photos, events, holidays, whatever.
--0-65087601-1137995906=:48256--


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

--===============0428084619==--




From ipcdn-bounces@ietf.org Tue Jan 24 08:33:05 2006
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 1F1OID-0006TP-IL; Tue, 24 Jan 2006 08:33:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1OI9-0006SW-IG
	for ipcdn@megatron.ietf.org; Tue, 24 Jan 2006 08:33:03 -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 IAA12066
	for <ipcdn@ietf.org>; Tue, 24 Jan 2006 08:31:30 -0500 (EST)
Received: from pacdcoavas10.cable.comcast.com ([208.17.33.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1ORh-0002EK-AM
	for ipcdn@ietf.org; Tue, 24 Jan 2006 08:42:53 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 24 Jan 2006 08:30:27 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF5C9@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: Inappropriate mail for IPCDN
Thread-Index: AcYf4lxAykXGCljcR7Oo2derJdCj3gBB3Oug
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Hassan Naser" <hnaser_ca@yahoo.com>
X-OriginalArrivalTime: 24 Jan 2006 13:32:10.0098 (UTC)
	FILETIME=[93D05D20:01C620EA]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: ipcdn@ietf.org
Subject: [ipcdn] Inappropriate mail for IPCDN
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="===============0478966451=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0478966451==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C620EA.935CFADD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C620EA.935CFADD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hassan,
=20
The IPCDN mailing list is for working group business only. Please do not
send email like the one below.
=20
Per RFC 3683, <http://www.ietf.org/rfc/rfc3683.txt>:
=20
   ... Although not exhaustive,
   examples of abusive or otherwise inappropriate postings to IETF
   mailing lists include:

   o  unsolicited bulk e-mail;

   o  discussion of subjects unrelated to IETF policy, meetings,
      activities, or technical concerns;

   o  unprofessional commentary, regardless of the general subject; and,

   o  announcements of conferences, events, or activities that are not
      sponsored or endorsed by the Internet Society or IETF.

-- Rich


-----Original Message-----
From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf
Of Hassan Naser
Sent: Monday, January 23, 2006 12:58 AM
To: ipcdn@ietf.org
Subject: [ipcdn] CFP: Special Session on Broadband Access Networks


(Apologies if you receive multiple copies of this CFP)
=20
C A L L   F O R   P A P E R S=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=3D=
=3D=3D=3D=3D=20
...=20


------_=_NextPart_001_01C620EA.935CFADD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office" xmlns:st1 =
=3D=20
"urn:schemas-microsoft-com:office:smarttags"><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=3D462412613-24012006>Hassan,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D462412613-24012006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D462412613-24012006>The=20
IPCDN mailing list is for working group business only. Please do not =
send email=20
like the one below.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D462412613-24012006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D462412613-24012006>Per=20
RFC 3683, =
&lt;http://www.ietf.org/rfc/rfc3683.txt&gt;:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D462412613-24012006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D462412613-24012006>&nbsp;&nbsp; ...=20
Although not exhaustive,<BR>&nbsp;&nbsp; examples of abusive or =
otherwise=20
inappropriate postings to IETF<BR>&nbsp;&nbsp; mailing lists=20
include:<BR><BR>&nbsp;&nbsp; o&nbsp; unsolicited bulk=20
e-mail;<BR><BR>&nbsp;&nbsp; o&nbsp; discussion of subjects unrelated to =
IETF=20
policy, meetings,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; activities, or =
technical=20
concerns;<BR><BR>&nbsp;&nbsp; o&nbsp; unprofessional commentary, =
regardless of=20
the general subject; and,<BR><BR>&nbsp;&nbsp; o&nbsp; announcements of=20
conferences, events, or activities that are=20
not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sponsored or endorsed by the =
Internet=20
Society or IETF.<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D462412613-24012006>--=20
Rich</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT size=3D2></FONT></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] <B>On Behalf Of =

  </B>Hassan Naser<BR><B>Sent:</B> Monday, January 23, 2006 12:58=20
  AM<BR><B>To:</B> ipcdn@ietf.org<BR><B>Subject:</B> [ipcdn] CFP: =
Special=20
  Session on Broadband Access Networks<BR><BR></FONT></DIV>
  <DIV id=3DRTEContent><PRE>(Apologies if you receive multiple copies of =
this CFP)</PRE><PRE><o:p>&nbsp;</o:p></PRE>
  <DIV class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Verdana">C A L L <SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</SPAN><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</SPAN>F O R <SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;</SPAN>P A P E R S=20
  <o:p></o:p></SPAN></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Verdana">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<SPAN=20
  class=3D462412613-24012006><FONT face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><SPAN=20
  class=3D462412613-24012006><FONT face=3DArial=20
  =
color=3D#0000ff>...</FONT>&nbsp;</SPAN><o:p></o:p></SPAN></DIV></DIV></BL=
OCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C620EA.935CFADD--


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

--===============0478966451==--




From ipcdn-bounces@ietf.org Tue Jan 24 16:57:15 2006
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 1F1WA7-00087A-TA; Tue, 24 Jan 2006 16:57:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1WA2-000872-4C
	for ipcdn@megatron.ietf.org; Tue, 24 Jan 2006 16:57:14 -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 QAA06488;
	Tue, 24 Jan 2006 16:55:38 -0500 (EST)
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F1WJc-0001mw-5S; Tue, 24 Jan 2006 17:07:07 -0500
Received: from ([10.20.9.174])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.16443279;
	Tue, 24 Jan 2006 16:56:40 -0500
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by
	PACDCEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 24 Jan 2006 16:56:40 -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
Date: Tue, 24 Jan 2006 16:56:39 -0500
Message-ID: <51D3159FBB1ACF408E61D37DCE9C50F6029507F7@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: Request for publication and PROTO writeup for
	draft-ietf-ipcdn-pktc-mtamib-09.txt on the standards track
Thread-Index: AcYhO4gr2AEXWQxYSRy/QAVLq0K+vg==
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Wijnen, Bert \(Bert\) " <bwijnen@lucent.com>, <iesg-secretary@ietf.org>
X-OriginalArrivalTime: 24 Jan 2006 21:56:40.0483 (UTC)
	FILETIME=[0E5E8F30:01C62131]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: quoted-printable
Cc: Jean-Francois Mule  <jf.mule@cablelabs.com>,
	Eugene Nechamkin  <enechamkin@broadcom.com>,
	"Ipcdn \(E-mail\) " <ipcdn@ietf.org>
Subject: [ipcdn] Request for publication and PROTO writeup for
	draft-ietf-ipcdn-pktc-mtamib-09.txt on the standards track
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 and all,

This note is the request for publication and proto write-up for the
IPCDN MTA MIB internet-draft, draft-ietf-ipcdn-pktc-mtamib-09.txt.=20

If you have any questions or concerns with the above, please send email
to the IPCDN list.

Thank you Jean-Francois and Eugene for your continued efforts and big
thanks to Randy Presuhn, Dave Thaler, Bert Wijnen et al. for the
detailed and constructive MIB doctor and expert reviews.

Richard Woundy
IPCDN Co-Chair


The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used for the IPCDN MTA MIB internet-draft.

Here is the PROTO writeup for:

Multimedia Terminal Adapter (MTA) Management Information Base for
PacketCable and IPCablecom compliant devices
(draft-ietf-ipcdn-pktc-mtamib-09.txt)

http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-09.txt=20

Requested Publication Status: Proposed Standard
PROTO shepherd: Richard Woundy (IPCDN WG Co-Chair)
------------------------------------------------------------------------

   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?

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, there have been 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. Most of the remaining WG comments were addressed at the IETF 64
meeting, and the draft update does resolve those open issues. There are
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
January 10 2006.
=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).
=20
There are no ID nits issues per the automated ID nits check (version
1.84) at:
<http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/draft-ietf-
ipcdn-pktc-mtamib-09.nits.txt>.

   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.

Note that there is a normative reference to the DOCSIS Cable Device MIB,
draft-ietf-ipcdn-device-mibv2-10.txt -- this draft has just completed
its own IETF Last Call.

Also note that there is an informative reference to the
PacketCable/IPCablecom NCS Signaling MIB,
draft-ietf-ipcdn-pktc-signaling-10.txt.

   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
=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 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=20
   Multimedia Terminal Adapter devices.=20
=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 Dave Thaler and Randy Presuhn; an
   earlier version of this MIB module was reviewed by Mike Heard.  The
   document has been reviewed by PacketCable/IPCablecom subject matter
   experts such as Thomas Anders, Sumanth Channabasappa, Satish Kumar,
and
   Matt Osman.  This document has been reviewed for the IESG by
   Bert Wijnen.
=20

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



From ipcdn-bounces@ietf.org Wed Jan 25 20:51:52 2006
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 1F1wIi-0004qr-T0; Wed, 25 Jan 2006 20:51:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1wIh-0004qj-2f; Wed, 25 Jan 2006 20:51:51 -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 UAA22536;
	Wed, 25 Jan 2006 20:50:19 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F1wSW-0005YH-SH; Wed, 25 Jan 2006 21:02:02 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k0Q1oe624118;
	Wed, 25 Jan 2006 17:50:40 -0800 (PST)
Message-Id: <200601260150.k0Q1oe624118@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 25 Jan 2006 17:50:40 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org
Subject: [ipcdn] RFC 4323 on Data Over Cable System Interface Specification
	Quality of Service Management Information Base (DOCSIS-QoS MIB)
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 Request for Comments is now available in online RFC libraries.


        RFC 4323

        Title:      Data Over Cable System Interface Specification
                    Quality of Service Management Information Base
                    (DOCSIS-QoS MIB)
        Author(s):  M. Patrick, W. Murwin
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    michael.patrick@motorola.com,
                    w.murwin@motorola.com
        Pages:      89
        Characters: 197285
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipcdn-qos-mib-12.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4323.txt


This document defines a basic set of managed objects for SNMP-based
management of extended QoS features of Cable Modems (CMs) and Cable
Modem Termination Systems (CMTSs) conforming to the Data over Cable
System (DOCSIS) specifications versions 1.1 and 2.0.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <060125174910.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4323

--OtherAccess
Content-Type: Message/External-body; name="rfc4323.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <060125174910.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--




From ipcdn-bounces@ietf.org Thu Jan 26 07:43:20 2006
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 1F26T9-0001E8-Vx; Thu, 26 Jan 2006 07:43:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F26T7-0001E0-Vq
	for ipcdn@megatron.ietf.org; Thu, 26 Jan 2006 07:43:18 -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 HAA09978
	for <ipcdn@ietf.org>; Thu, 26 Jan 2006 07:41:46 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F26d4-0001vz-AN
	for ipcdn@ietf.org; Thu, 26 Jan 2006 07:53:35 -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 k0QCgw9q018650;
	Thu, 26 Jan 2006 05:42:59 -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
Subject: RE: [ipcdn] RFC 4323 on Data Over Cable System Interface
	SpecificationQuality of Service Management Information Base
	(DOCSIS-QoS MIB)
Date: Thu, 26 Jan 2006 05:42:58 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804013CDB61@srvxchg.cablelabs.com>
Thread-Topic: [ipcdn] RFC 4323 on Data Over Cable System Interface
	SpecificationQuality of Service Management Information Base
	(DOCSIS-QoS MIB)
Thread-Index: AcYiG2VvUQadYcoJSdGk475fXIlcsAAWoKQw
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <michael.patrick@motorola.com>, <w.murwin@motorola.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable
Cc: 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

Mike and Will,

   Thanks for all the work you both did on the ipcdn qos mib and many =
thanks to all of you who contributed to this work.

Jean-Fran=E7ois
> -----Original Message-----
> From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> Sent: Wednesday, January 25, 2006 6:51 PM
> To: ietf-announce@ietf.org
> Cc: ipcdn@ietf.org; rfc-editor@rfc-editor.org
> Subject: [ipcdn] RFC 4323 on Data Over Cable System Interface
> SpecificationQuality of Service Management Information Base (DOCSIS-
> QoS MIB)
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>         RFC 4323
>=20
>         Title:      Data Over Cable System Interface Specification
>                     Quality of Service Management Information Base
>                     (DOCSIS-QoS MIB)
>         Author(s):  M. Patrick, W. Murwin
>         Status:     Standards Track
>         Date:       January 2006
>         Mailbox:    michael.patrick@motorola.com,
>                     w.murwin@motorola.com
>         Pages:      89
>         Characters: 197285
>         Updates/Obsoletes/SeeAlso:    None
>=20
>         I-D Tag:    draft-ietf-ipcdn-qos-mib-12.txt
>=20
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4323.txt
>=20
>=20
> This document defines a basic set of managed objects for SNMP-based
> management of extended QoS features of Cable Modems (CMs) and Cable
> Modem Termination Systems (CMTSs) conforming to the Data over Cable
> System (DOCSIS) specifications versions 1.1 and 2.0.
>=20
> This document is a product of the IP over Cable Data Network Working
> Group of the IETF.
>=20
> This is now a Proposed Standard Protocol.
>=20
> This document specifies an Internet standards track protocol for
> the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the
> "Internet Official Protocol Standards" (STD 1) for the
> standardization state and status of this protocol.  Distribution
> of this memo is unlimited.
>=20
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>=20
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> help: ways_to_get_rfcs.  For example:
>=20
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>=20
>         help: ways_to_get_rfcs
>=20
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>=20
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to
> RFC
> Authors, for further information.
>=20
>=20
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
>=20
> ...
>=20
> Below is the data which will enable a MIME compliant Mail Reader
> implementation to automatically retrieve the ASCII version
> of the RFCs.


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



From ipcdn-bounces@ietf.org Sun Jan 29 14:56:40 2006
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 1F3If9-0007Gl-U6; Sun, 29 Jan 2006 14:56:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F3If8-0007Gd-RJ
	for ipcdn@megatron.ietf.org; Sun, 29 Jan 2006 14:56:39 -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 OAA22294
	for <ipcdn@ietf.org>; Sun, 29 Jan 2006 14:55:01 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3Ipj-0001UM-Eu
	for ipcdn@ietf.org; Sun, 29 Jan 2006 15:07:35 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k0TJuJKv013172; 
	Sun, 29 Jan 2006 13:56:19 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <DVB4FSBQ>; Sun, 29 Jan 2006 20:56:12 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155092F5117@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
Date: Sun, 29 Jan 2006 20:56:06 +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: ec7c6dab5a62df223002ae71b5179d41
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>,
	Eugene Nechamkin <enechamkin@broadcom.com>,
	"Ipcdn \(E-mail\) " <ipcdn@ietf.org>
Subject: [ipcdn] RE: Request for publication and PROTO writeup for
	draft-ietf-ipcd n-pktc-mtamib-09.txt on the standards track
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

Thanks,
I have now requested IETF Last Call.
Probably will show up on Monday.

Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com]
> Sent: Tuesday, January 24, 2006 13:57
> To: Wijnen, Bert (Bert) ; iesg-secretary@ietf.org
> Cc: Jean-Francois Mule ; Eugene Nechamkin ; Ipcdn (E-mail) 
> Subject: Request for publication and PROTO writeup for
> draft-ietf-ipcdn-pktc-mtamib-09.txt on the standards track
> 
> 
> Bert and all,
> 
> This note is the request for publication and proto write-up for the
> IPCDN MTA MIB internet-draft, draft-ietf-ipcdn-pktc-mtamib-09.txt. 
> 
> If you have any questions or concerns with the above, please 
> send email
> to the IPCDN list.
> 
> Thank you Jean-Francois and Eugene for your continued efforts and big
> thanks to Randy Presuhn, Dave Thaler, Bert Wijnen et al. for the
> detailed and constructive MIB doctor and expert reviews.
> 
> Richard Woundy
> IPCDN Co-Chair
> 
> 
> The PROTO process (cf. 
> draft-ietf-proto-wgchair-doc-shepherding-05.txt)
> is being used for the IPCDN MTA MIB internet-draft.
> 
> Here is the PROTO writeup for:
> 
> Multimedia Terminal Adapter (MTA) Management Information Base for
> PacketCable and IPCablecom compliant devices
> (draft-ietf-ipcdn-pktc-mtamib-09.txt)
> 
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtam
> ib-09.txt 
> 
> Requested Publication Status: Proposed Standard
> PROTO shepherd: Richard Woundy (IPCDN WG Co-Chair)
> --------------------------------------------------------------
> ----------
> 
>    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?
> 
> 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.
>  
>  
>    1.b) Has the document had adequate review from both key WG members
>         and key non-WG members?
>  
> Yes, there have been 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.
>  
>  
>         Do you have any concerns about the
>         depth or breadth of the reviews that have been performed?
>  
> No, given the time this ID has been in existence and the number of
> revisions due to comments.
>  
>  
>    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.)?
>  
> No.
>  
>    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.
>  
> No. Most of the remaining WG comments were addressed at the IETF 64
> meeting, and the draft update does resolve those open issues. 
> There are
> no other concerns from the PROTO shepherd.
>  
>    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?
>  
> This document represents the WG consensus as a whole: the WG 
> as a whole
> understands and agrees with it.
>  
>    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.
>  
> No. An explicit request for intent to appeal was made on the list on
> January 10 2006.
>  
>    1.g) Have the chairs verified that the document adheres to 
> all of the
>         ID nits? (see http://www.ietf.org/ID-Checklist.html).
>  
> There are no ID nits issues per the automated ID nits check (version
> 1.84) at:
> <http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-mtamib/d
> raft-ietf-
> ipcdn-pktc-mtamib-09.nits.txt>.
> 
>    1.h) Is the document split into normative and informative 
> references?
>  
> Yes.
>  
>         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.)
>  
> No.
> 
> Note that there is a normative reference to the DOCSIS Cable 
> Device MIB,
> draft-ietf-ipcdn-device-mibv2-10.txt -- this draft has just completed
> its own IETF Last Call.
> 
> Also note that there is an informative reference to the
> PacketCable/IPCablecom NCS Signaling MIB,
> draft-ietf-ipcdn-pktc-signaling-10.txt.
> 
>    1.i) For Standards Track and BCP documents, the IESG approval
>         announcement includes a write-up section with the following
>         sections:
>  
>         *    Technical Summary
>  
>         *    Working Group Summary
>  
>         *    Protocol Quality
>  
>    1.j) Please provide such a write-up.  Recent examples can 
> be found in
>         the "protocol action" announcements for approved documents.
>  
> --- Technical Summary
>  
>    This document 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. 
>  
>  
> --- Working Group Summary
>  
>    The Working Group has consensus to publish this document as a
>    Proposed Standard.
>  
>  
> --- Protocol Quality
>  
>    The MIB module has been reviewed by Dave Thaler and Randy 
> Presuhn; an
>    earlier version of this MIB module was reviewed by Mike Heard.  The
>    document has been reviewed by PacketCable/IPCablecom subject matter
>    experts such as Thomas Anders, Sumanth Channabasappa, Satish Kumar,
> and
>    Matt Osman.  This document has been reviewed for the IESG by
>    Bert Wijnen.
>  
> 

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



From ipcdn-bounces@ietf.org Mon Jan 30 11:45:55 2006
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 1F3cA7-0001Py-SV; Mon, 30 Jan 2006 11:45:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3cA3-0001P8-Na; Mon, 30 Jan 2006 11:45:51 -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 LAA06225;
	Mon, 30 Jan 2006 11:44:17 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3cKr-0001RA-Or; Mon, 30 Jan 2006 11:57:01 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1F3cA2-00065V-UY; Mon, 30 Jan 2006 11:45:50 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1F3cA2-00065V-UY@newodin.ietf.org>
Date: Mon, 30 Jan 2006 11:45:50 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ipcdn@ietf.org
Subject: [ipcdn] Last Call: 'Multimedia Terminal Adapter (MTA) Management
 Information 
 Base for PacketCable and IPCablecom compliant devices' 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:

- 'Multimedia Terminal Adapter (MTA) Management Information Base for 
   PacketCable and IPCablecom compliant devices '
   <draft-ietf-ipcdn-pktc-mtamib-09.txt> as a Proposed Standard

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 2006-02-13.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-09.txt


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



From ipcdn-bounces@ietf.org Tue Jan 31 10:26:26 2006
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 1F3xOk-0004PT-4o; Tue, 31 Jan 2006 10:26:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F3xOi-0004Hh-4l
	for ipcdn@megatron.ietf.org; Tue, 31 Jan 2006 10:26:24 -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 KAA26538;
	Tue, 31 Jan 2006 10:24:34 -0500 (EST)
Received: from pacdcoavas10.cable.comcast.com ([208.17.33.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3xZR-0007OG-Ab; Tue, 31 Jan 2006 10:37:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 Jan 2006 10:25:31 -0500
Message-ID: <51D3159FBB1ACF408E61D37DCE9C50F602954E03@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: Request for publication and PROTO writeup for
	draft-ietf-ipcdn-docs-rfmibv2-14.txt on the standards track
Thread-Index: AcYmepK/ToG1UhZpQraa5ecg4qp8LA==
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>, <iesg-secretary@ietf.org>
X-OriginalArrivalTime: 31 Jan 2006 15:25:32.0436 (UTC)
	FILETIME=[93370540:01C6267A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: quoted-printable
Cc: Eduardo Cardona <e.cardona@CableLabs.com>,
	"Ipcdn \(E-mail\)" <ipcdn@ietf.org>
Subject: [ipcdn] Request for publication and PROTO writeup for
	draft-ietf-ipcdn-docs-rfmibv2-14.txt on the standards track
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 and all,=20

This note is the request for publication and proto write-up for the =
IPCDN DOCSIS RFIv2 MIB internet-draft, =
draft-ietf-ipcdn-docs-rfmibv2-14.txt, as a Proposed Standard.

If you have any questions or concerns with the above, please send email =
to the IPCDN list.=20

Thank you Eugene for your continued efforts and big thanks to Randy, =
Bert et al. for the detailed and constructive MIB doctor and expert =
reviews.

Richard Woundy=20
IPCDN Co-Chair=20


The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt) =
is being used for the IPCDN DOCSIS RFIv2 MIB internet-draft.

Here is the proposed PROTO writeup for:=20

Radio Frequency (RF) Interface Management Information Base for DOCSIS =
2.0 compliant RF interfaces=20
(draft-ietf-ipcdn-docs-rfmibv2-14.txt)=20

http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt =



Requested Publication Status: Proposed Standard=20
Obsoletes: RFC 2670=20
PROTO shepherd: Richard Woundy (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=20
        to forward to the IESG for publication?=20

Yes.=20

Both IPCDN co-chairs reviewed this version of the ID. Based on the WG =
comments, MIB doctors & AD review comments, we believe the ID is ready =
for publication.

   1.b) Has the document had adequate review from both key WG members=20
        and key non-WG members?=20

Yes, there have been 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.

        Do you have any concerns about the=20
        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

   1.c) Do you have concerns that the document needs more review from a=20
        particular (broader) perspective (e.g., security, operational=20
        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=20
        example, perhaps you are uncomfortable with certain parts of the =

        document, or have concerns whether there really is a need for=20
        it.  In any event, if your issues have been discussed in the WG=20
        and the WG has indicated it that it still wishes to advance the=20
        document, detail those concerns in the write-up.=20

No. The internet-draft was produced prior to the IETF 64 meeting, based =
on comments from the AD review. No further issues were raised on this =
internet-draft at the IETF 64 meeting, nor subsequently on the WG =
mailing list. There are no other concerns from the PROTO shepherd.

   1.e) How solid is the WG consensus behind this document? Does it=20
        represent the strong concurrence of a few individuals, with=20
        others being silent, or does the WG as a whole understand and=20
        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=20
        discontent?  If so, please summarise the areas of conflict in=20
        separate email to the Responsible Area Director.=20

No. An explicit request for intent to appeal was made on the list on =
January 10 2006.=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).=20

There are no ID nits issues per the automated ID nits check (version =
1.82) at:=20
<http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-docs-rfmibv2/draft-ietf-=
ipcdn-docs-rfmibv2-14.nits.txt>=20

   1.h) Is the document split into normative and informative references? =


Yes.=20

        Are there normative references to IDs, where the IDs are not=20
        also ready for advancement or are otherwise in an unclear state? =

        (note here that the RFC editor will not publish an RFC with=20
        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=20
        announcement includes a write-up section with the following=20
        sections:=20

        *    Technical Summary=20

        *    Working Group Summary=20

        *    Protocol Quality=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 2670, and=20
   defines a portion of the Management Information Base (MIB) for=20
   use with network management protocols in the Internet community.=20
   In particular, it defines a set of managed objects for SNMP-based=20
   management of the Radio Frequency (RF) interfaces for systems=20
   compliant with the Data Over Cable Service Interface Specifications=20
   (DOCSIS).=20

--- Working Group Summary=20

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

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


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



