From ipcdn-admin@ietf.org  Fri May 11 07:19:30 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04152;
	Fri, 11 May 2001 07:19:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18754;
	Fri, 11 May 2001 07:12:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18731
	for <ipcdn@ns.ietf.org>; Fri, 11 May 2001 07:12:51 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03794;
	Fri, 11 May 2001 07:12:44 -0400 (EDT)
Message-Id: <200105111112.HAA03794@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ipcdn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 11 May 2001 07:12:44 -0400
Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org

--NextPart

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

	Title		: Management Information Base for DOCSIS Cable Modems 
                          and Cable Modem Termination Systems                  
                          for Baseline Privacy Plus
	Author(s)	: S. Green
	Filename	: draft-ietf-ipcdn-bpiplus-mib-05.txt
	Pages		: 66
	Date		: 10-May-01
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a set of managed objects for SNMP-based
management of the Baseline Privacy Plus features [17] of
DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
Systems.
This memo specifies a MIB module in a manner that is compliant to the
SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
SNMP framework and existing SNMP standards.
This memo is a product of the IPCDN working group within the Internet
Engineering Task Force.  Comments are solicited and should be
addressed to the working group's mailing list at ipcdn@terayon.com
and/or the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ipcdn-bpiplus-mib-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010510110327.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt

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

Content-Type: text/plain
Content-ID:	<20010510110327.I-D@ietf.org>

--OtherAccess--

--NextPart--



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


From ipcdn-admin@ietf.org  Tue May 15 19:53:29 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09918;
	Tue, 15 May 2001 19:53:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA29226;
	Tue, 15 May 2001 19:53:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA29207
	for <ipcdn@ns.ietf.org>; Tue, 15 May 2001 19:53:00 -0400 (EDT)
Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09911
	for <ipcdn@ietf.org>; Tue, 15 May 2001 19:52:51 -0400 (EDT)
Received: from dhegglin-ultra.yagosys.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id QAA04192; Tue, 15 May 2001 16:52:28 -0700 (PDT)
Received: from DHEGGLINLAPTOP by dhegglin-ultra.yagosys.com (SMI-8.6/SMI-SVR4)
	id QAA00548; Tue, 15 May 2001 16:52:27 -0700
From: "Daniel Hegglin" <dhegglin@riverstonenet.com>
To: <ipcdn@ietf.org>, <ipcdn@terayon.com>
Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
Date: Tue, 15 May 2001 16:58:13 -0700
Message-ID: <001101c0dd9a$e6b8d9b0$2aac8d86@DHEGGLINLAPTOP>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <200105111112.HAA03794@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org
Content-Transfer-Encoding: 7bit

A few questions regarding the mib:

1. The docsBpi2CmtsIpMulticastTable now has information in it that is
redundant with the TEK table, specifically:
- DataEncryptAlg
- DataAuthentAlg
- SAType
Is there a reason these variables were added to the table?

2. IpMulticastSAId has a range of 0..16383.  This is incorrect as it also
includes non-multicast SIDs.

3. When a CM requests a mapping for a multicast IP address that does NOT
exist, we send the CM the appropriate reject message.  The problem is that
we don't have an entry in this table if there is no mapping, hance the
SAMapRejectErrorCode can never be set to noAuthForRequestedDSFlow(9), making
it superfluous.  Am I missing something?

4. What was the motivation to change the indexing to this table?

thanks!
dan

> -----Original Message-----
> From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Friday, May 11, 2001 4:13 AM
> To: IETF-Announce:; @ietf.org@manet
> Cc: ipcdn@ietf.org
> Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
>
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the IP over Cable Data Network
> Working Group of the IETF.
>
> 	Title		: Management Information Base for DOCSIS
> Cable Modems
>                           and Cable Modem Termination Systems
>
>                           for Baseline Privacy Plus
> 	Author(s)	: S. Green
> 	Filename	: draft-ietf-ipcdn-bpiplus-mib-05.txt
> 	Pages		: 66
> 	Date		: 10-May-01
>
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in the Internet community.
> In particular, it defines a set of managed objects for SNMP-based
> management of the Baseline Privacy Plus features [17] of
> DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> Systems.
> This memo specifies a MIB module in a manner that is compliant to the
> SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> SNMP framework and existing SNMP standards.
> This memo is a product of the IPCDN working group within the Internet
> Engineering Task Force.  Comments are solicited and should be
> addressed to the working group's mailing list at ipcdn@terayon.com
> and/or the authors.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with
> the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-ipcdn-bpiplus-mib-05.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


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


From ipcdn-admin@ietf.org  Wed May 16 20:16:25 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21555;
	Wed, 16 May 2001 20:16:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA27058;
	Wed, 16 May 2001 20:13:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA27033
	for <ipcdn@ns.ietf.org>; Wed, 16 May 2001 20:13:32 -0400 (EDT)
Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21523
	for <ipcdn@ietf.org>; Wed, 16 May 2001 20:13:24 -0400 (EDT)
Received: from dhegglin-ultra.yagosys.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id RAA08402; Wed, 16 May 2001 17:12:57 -0700 (PDT)
Received: from DHEGGLINLAPTOP by dhegglin-ultra.yagosys.com (SMI-8.6/SMI-SVR4)
	id RAA00529; Wed, 16 May 2001 17:12:56 -0700
From: "Daniel Hegglin" <dhegglin@riverstonenet.com>
To: "Stuart Green" <stu.green@ne.arris-i.com>
Cc: <ipcdn@ietf.org>, <ipcdn@terayon.com>
Subject: RE: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
Date: Wed, 16 May 2001 17:18:43 -0700
Message-ID: <002501c0de66$ee4b5a00$0353870a@DHEGGLINLAPTOP>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <3B030D4A.8AE93335@ne.arris-i.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org
Content-Transfer-Encoding: 7bit

Stuart,

> > 1. The docsBpi2CmtsIpMulticastTable now has information in it that is
> > redundant with the TEK table, specifically:
> > - DataEncryptAlg
> > - DataAuthentAlg
> > - SAType
> > Is there a reason these variables were added to the table?
> >
>
> If a CMTS implements "create access" for a new multicast SAID,
> these 3 fields need to be specified.

Hmmm, I agree on the dataEncryptAlg & dataAuthentAlg, but why the SAType?
Is it ok if I set the type to be primary if the SAId is in the multicast
range?  I guess there's other places in the spec where the operator can set
unreasonable values.

I'm also a bit confused on the static/dynamic designation.  If I statically
define a multicast mapping and define a static entry in the multicast
authorization table for modem x, that makes it a static entry.  However, if
modem y sends a SAMap requesting this mapping, it is technically a dynamic
mapping for modem y, but the designation still stays static.  There are
other scenarios like this, but to me it's not very clear from the spec since
it can be static to one modem and dynamic to another.  My approach has been
to declare any entry static if there are entries statically defined in the
multicast authorization table using SNMP, even if this occurs after it is
already designated dynamic through a SAMap request.  Is this the proper
approach?

> > 3. When a CM requests a mapping for a multicast IP address that does NOT
> > exist, we send the CM the appropriate reject message.  The
> problem is that
> > we don't have an entry in this table if there is no mapping, hance the
> > SAMapRejectErrorCode can never be set to
> noAuthForRequestedDSFlow(9), making
> > it superfluous.  Am I missing something?

Whoops, my bad.  What I meant is dsFlowNotMappedToSA(10).  If there is no
mapping then there is no entry in this table.  If there is no entry in this
table, then we can never set this to 10.  If there is a mapping, then we
would never set it to 10.  Does this make dsFlowNotMappedToSA superfluous?

thanks,
dan

> > > -----Original Message-----
> > > From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> > > Internet-Drafts@ietf.org
> > > Sent: Friday, May 11, 2001 4:13 AM
> > > To: IETF-Announce:; @ietf.org@manet
> > > Cc: ipcdn@ietf.org
> > > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line
> > > Internet-Drafts directories.
> > > This draft is a work item of the IP over Cable Data Network
> > > Working Group of the IETF.
> > >
> > >       Title           : Management Information Base for DOCSIS
> > > Cable Modems
> > >                           and Cable Modem Termination Systems
> > >
> > >                           for Baseline Privacy Plus
> > >       Author(s)       : S. Green
> > >       Filename        : draft-ietf-ipcdn-bpiplus-mib-05.txt
> > >       Pages           : 66
> > >       Date            : 10-May-01
> > >
> > > This memo defines a portion of the Management Information Base (MIB)
> > > for use with network management protocols in the Internet community.
> > > In particular, it defines a set of managed objects for SNMP-based
> > > management of the Baseline Privacy Plus features [17] of
> > > DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> > > Systems.
> > > This memo specifies a MIB module in a manner that is compliant to the
> > > SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> > > SNMP framework and existing SNMP standards.
> > > This memo is a product of the IPCDN working group within the Internet
> > > Engineering Task Force.  Comments are solicited and should be
> > > addressed to the working group's mailing list at ipcdn@terayon.com
> > > and/or the authors.
> > >
> > > A URL for this Internet-Draft is:
> > >
> http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
> > >
> > > Internet-Drafts are also available by anonymous FTP. Login with
> > > the username
> > > "anonymous" and a password of your e-mail address. After logging in,
> > > type "cd internet-drafts" and then
> > >       "get draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > >
> > > A list of Internet-Drafts directories can be found in
> > > http://www.ietf.org/shadow.html
> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > >
> > >
> > > Internet-Drafts can also be obtained by e-mail.
> > >
> > > Send a message to:
> > >       mailserv@ietf.org.
> > > In the body type:
> > >       "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > >
> > > NOTE: The mail server at ietf.org can return the document in
> > >       MIME-encoded form by using the "mpack" utility.  To use this
> > >       feature, insert the command "ENCODING mime" before the "FILE"
> > >       command.  To decode the response(s), you will need "munpack" or
> > >       a MIME-compliant mail reader.  Different MIME-compliant
> mail readers
> > >       exhibit different behavior, especially when dealing with
> > >       "multipart" MIME messages (i.e. documents which have been split
> > >       up into multiple messages), so check your local documentation on
> > >       how to manipulate these messages.
> > >
> > >
> > > Below is the data which will enable a MIME compliant mail reader
> > > implementation to automatically retrieve the ASCII version of the
> > > Internet-Draft.
> > >
> >
> > _______________________________________________
> > IPCDN mailing list
> > IPCDN@ietf.org
> > http://www1.ietf.org/mailman/listinfo/ipcdn
>


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


From owner-ipcdn@terayon.com  Wed May 16 22:35:51 2001
Received: from terayon.com (mails.terayon.com [63.201.251.36])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA24638
	for <ipcdn-archive@odin.ietf.org>; Wed, 16 May 2001 22:35:50 -0400 (EDT)
Received: (from root@localhost)
	by terayon.com (8.9.3+Sun/8.9.3) id QAA13985
	for ipcdn-outgoing; Wed, 16 May 2001 16:37:39 -0700 (PDT)
Message-ID: <3B030D4A.8AE93335@ne.arris-i.com>
Date: Wed, 16 May 2001 19:29:14 -0400
From: Stuart Green <stu.green@ne.arris-i.com>
Organization: Nortel Networks - Arris Venture
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Hegglin <dhegglin@riverstonenet.com>
CC: ipcdn@ietf.org, ipcdn@terayon.com
Subject: Re: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
References: <001101c0dd9a$e6b8d9b0$2aac8d86@DHEGGLINLAPTOP>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipcdn@terayon.com
Precedence: bulk
Reply-To: ipcdn@terayon.com
Content-Transfer-Encoding: 7bit

Daniel,
  See below.
-- 
Stuart Green
Nortel Networks - Arris Venture


Daniel Hegglin wrote:
> 
> A few questions regarding the mib:
> 
> 1. The docsBpi2CmtsIpMulticastTable now has information in it that is
> redundant with the TEK table, specifically:
> - DataEncryptAlg
> - DataAuthentAlg
> - SAType
> Is there a reason these variables were added to the table?
> 

If a CMTS implements "create access" for a new multicast SAID, 
these 3 fields need to be specified.


> 2. IpMulticastSAId has a range of 0..16383.  This is incorrect as it also
> includes non-multicast SIDs.
> 

A CMTS could provide the capability of mapping a multicast IP address
to the primary SID, thus extending the SAID range. 


> 3. When a CM requests a mapping for a multicast IP address that does NOT
> exist, we send the CM the appropriate reject message.  The problem is that
> we don't have an entry in this table if there is no mapping, hance the
> SAMapRejectErrorCode can never be set to noAuthForRequestedDSFlow(9), making
> it superfluous.  Am I missing something?
> 

If the multicast IP address does not exist, the error can not be
logged in the table.  However, if the address exists then 
noAuthForRequestDSFlow could occur and should be reflected
in the table.

> 4. What was the motivation to change the indexing to this table?
> 

IP address needed to change in order to be "IPv6 ready".
The decision to move the IP address out of the index was a
difficult one; in the end, we opted for a simple index 
rather than a complicated but (IP) ordered index.

> thanks!
> dan
> 
> > -----Original Message-----
> > From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> > Internet-Drafts@ietf.org
> > Sent: Friday, May 11, 2001 4:13 AM
> > To: IETF-Announce:; @ietf.org@manet
> > Cc: ipcdn@ietf.org
> > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
> >
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the IP over Cable Data Network
> > Working Group of the IETF.
> >
> >       Title           : Management Information Base for DOCSIS
> > Cable Modems
> >                           and Cable Modem Termination Systems
> >
> >                           for Baseline Privacy Plus
> >       Author(s)       : S. Green
> >       Filename        : draft-ietf-ipcdn-bpiplus-mib-05.txt
> >       Pages           : 66
> >       Date            : 10-May-01
> >
> > This memo defines a portion of the Management Information Base (MIB)
> > for use with network management protocols in the Internet community.
> > In particular, it defines a set of managed objects for SNMP-based
> > management of the Baseline Privacy Plus features [17] of
> > DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> > Systems.
> > This memo specifies a MIB module in a manner that is compliant to the
> > SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> > SNMP framework and existing SNMP standards.
> > This memo is a product of the IPCDN working group within the Internet
> > Engineering Task Force.  Comments are solicited and should be
> > addressed to the working group's mailing list at ipcdn@terayon.com
> > and/or the authors.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
> >
> > Internet-Drafts are also available by anonymous FTP. Login with
> > the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >       "get draft-ietf-ipcdn-bpiplus-mib-05.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> >       mailserv@ietf.org.
> > In the body type:
> >       "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> >       MIME-encoded form by using the "mpack" utility.  To use this
> >       feature, insert the command "ENCODING mime" before the "FILE"
> >       command.  To decode the response(s), you will need "munpack" or
> >       a MIME-compliant mail reader.  Different MIME-compliant mail readers
> >       exhibit different behavior, especially when dealing with
> >       "multipart" MIME messages (i.e. documents which have been split
> >       up into multiple messages), so check your local documentation on
> >       how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >
> 
> _______________________________________________
> IPCDN mailing list
> IPCDN@ietf.org
> http://www1.ietf.org/mailman/listinfo/ipcdn


From ipcdn-admin@ietf.org  Thu May 17 10:54:24 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19023;
	Thu, 17 May 2001 10:54:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04877;
	Thu, 17 May 2001 10:44:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25791
	for <ipcdn@ns.ietf.org>; Wed, 16 May 2001 19:37:25 -0400 (EDT)
Received: from ne.arris-i.com ([206.135.68.101])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA21259
	for <ipcdn@ietf.org>; Wed, 16 May 2001 19:37:18 -0400 (EDT)
Received: from ne.arris-i.com (belafonte.ne.arris-i.com [141.251.36.84])
	by ne.arris-i.com (8.11.2/9.0.0) with ESMTP id f4GNcws06105;
	Wed, 16 May 2001 19:38:58 -0400 (EDT)
Message-ID: <3B030D4A.8AE93335@ne.arris-i.com>
Date: Wed, 16 May 2001 19:29:14 -0400
From: Stuart Green <stu.green@ne.arris-i.com>
Organization: Nortel Networks - Arris Venture
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Hegglin <dhegglin@riverstonenet.com>
CC: ipcdn@ietf.org, ipcdn@terayon.com
Subject: Re: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
References: <001101c0dd9a$e6b8d9b0$2aac8d86@DHEGGLINLAPTOP>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org
Content-Transfer-Encoding: 7bit

Daniel,
  See below.
-- 
Stuart Green
Nortel Networks - Arris Venture


Daniel Hegglin wrote:
> 
> A few questions regarding the mib:
> 
> 1. The docsBpi2CmtsIpMulticastTable now has information in it that is
> redundant with the TEK table, specifically:
> - DataEncryptAlg
> - DataAuthentAlg
> - SAType
> Is there a reason these variables were added to the table?
> 

If a CMTS implements "create access" for a new multicast SAID, 
these 3 fields need to be specified.


> 2. IpMulticastSAId has a range of 0..16383.  This is incorrect as it also
> includes non-multicast SIDs.
> 

A CMTS could provide the capability of mapping a multicast IP address
to the primary SID, thus extending the SAID range. 


> 3. When a CM requests a mapping for a multicast IP address that does NOT
> exist, we send the CM the appropriate reject message.  The problem is that
> we don't have an entry in this table if there is no mapping, hance the
> SAMapRejectErrorCode can never be set to noAuthForRequestedDSFlow(9), making
> it superfluous.  Am I missing something?
> 

If the multicast IP address does not exist, the error can not be
logged in the table.  However, if the address exists then 
noAuthForRequestDSFlow could occur and should be reflected
in the table.

> 4. What was the motivation to change the indexing to this table?
> 

IP address needed to change in order to be "IPv6 ready".
The decision to move the IP address out of the index was a
difficult one; in the end, we opted for a simple index 
rather than a complicated but (IP) ordered index.

> thanks!
> dan
> 
> > -----Original Message-----
> > From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> > Internet-Drafts@ietf.org
> > Sent: Friday, May 11, 2001 4:13 AM
> > To: IETF-Announce:; @ietf.org@manet
> > Cc: ipcdn@ietf.org
> > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
> >
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the IP over Cable Data Network
> > Working Group of the IETF.
> >
> >       Title           : Management Information Base for DOCSIS
> > Cable Modems
> >                           and Cable Modem Termination Systems
> >
> >                           for Baseline Privacy Plus
> >       Author(s)       : S. Green
> >       Filename        : draft-ietf-ipcdn-bpiplus-mib-05.txt
> >       Pages           : 66
> >       Date            : 10-May-01
> >
> > This memo defines a portion of the Management Information Base (MIB)
> > for use with network management protocols in the Internet community.
> > In particular, it defines a set of managed objects for SNMP-based
> > management of the Baseline Privacy Plus features [17] of
> > DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> > Systems.
> > This memo specifies a MIB module in a manner that is compliant to the
> > SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> > SNMP framework and existing SNMP standards.
> > This memo is a product of the IPCDN working group within the Internet
> > Engineering Task Force.  Comments are solicited and should be
> > addressed to the working group's mailing list at ipcdn@terayon.com
> > and/or the authors.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
> >
> > Internet-Drafts are also available by anonymous FTP. Login with
> > the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >       "get draft-ietf-ipcdn-bpiplus-mib-05.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> >       mailserv@ietf.org.
> > In the body type:
> >       "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> >       MIME-encoded form by using the "mpack" utility.  To use this
> >       feature, insert the command "ENCODING mime" before the "FILE"
> >       command.  To decode the response(s), you will need "munpack" or
> >       a MIME-compliant mail reader.  Different MIME-compliant mail readers
> >       exhibit different behavior, especially when dealing with
> >       "multipart" MIME messages (i.e. documents which have been split
> >       up into multiple messages), so check your local documentation on
> >       how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >
> 
> _______________________________________________
> IPCDN mailing list
> IPCDN@ietf.org
> http://www1.ietf.org/mailman/listinfo/ipcdn


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


From owner-ipcdn@terayon.com  Fri May 18 23:46:01 2001
Received: from terayon.com (mails.terayon.com [63.201.251.36])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA24410
	for <ipcdn-archive@odin.ietf.org>; Fri, 18 May 2001 23:46:00 -0400 (EDT)
Received: (from root@localhost)
	by terayon.com (8.9.3+Sun/8.9.3) id RAA26778
	for ipcdn-outgoing; Fri, 18 May 2001 17:36:46 -0700 (PDT)
Message-ID: <3B05BE27.FCF39418@ne.arris-i.com>
Date: Fri, 18 May 2001 20:28:23 -0400
From: Stuart Green <stu.green@ne.arris-i.com>
Organization: Nortel Networks - Arris Venture
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Hegglin <dhegglin@riverstonenet.com>
CC: ipcdn@ietf.org, ipcdn@terayon.com
Subject: Re: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
References: <002501c0de66$ee4b5a00$0353870a@DHEGGLINLAPTOP>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ipcdn@terayon.com
Precedence: bulk
Reply-To: ipcdn@terayon.com
Content-Transfer-Encoding: 7bit

Daniel Hegglin wrote:
> 
> Stuart,
> 
> > > 1. The docsBpi2CmtsIpMulticastTable now has information in it that is
> > > redundant with the TEK table, specifically:
> > > - DataEncryptAlg
> > > - DataAuthentAlg
> > > - SAType
> > > Is there a reason these variables were added to the table?
> > >
> >
> > If a CMTS implements "create access" for a new multicast SAID,
> > these 3 fields need to be specified.
> 
> Hmmm, I agree on the dataEncryptAlg & dataAuthentAlg, but why the SAType?
> Is it ok if I set the type to be primary if the SAId is in the multicast
> range?  I guess there's other places in the spec where the operator can set
> unreasonable values.

The table is meant to be general purpose as it is difficult to predict
exactly how multicast services will be rolled out.  Your specific 
implementation may choose not to allow multicast mapping to primary
SAIDs.


> 
> I'm also a bit confused on the static/dynamic designation.  If I statically
> define a multicast mapping and define a static entry in the multicast
> authorization table for modem x, that makes it a static entry.  However, if
> modem y sends a SAMap requesting this mapping, it is technically a dynamic
> mapping for modem y, but the designation still stays static.  There are
> other scenarios like this, but to me it's not very clear from the spec since
> it can be static to one modem and dynamic to another.  My approach has been
> to declare any entry static if there are entries statically defined in the
> multicast authorization table using SNMP, even if this occurs after it is
> already designated dynamic through a SAMap request.  Is this the proper
> approach?

Yes I believe your implementation is acceptable and the static/dynamic
designation is arbitrary for BPI+.  


> 
> > > 3. When a CM requests a mapping for a multicast IP address that does NOT
> > > exist, we send the CM the appropriate reject message.  The
> > problem is that
> > > we don't have an entry in this table if there is no mapping, hance the
> > > SAMapRejectErrorCode can never be set to
> > noAuthForRequestedDSFlow(9), making
> > > it superfluous.  Am I missing something?
> 
> Whoops, my bad.  What I meant is dsFlowNotMappedToSA(10).  If there is no
> mapping then there is no entry in this table.  If there is no entry in this
> table, then we can never set this to 10.  If there is a mapping, then we
> would never set it to 10.  Does this make dsFlowNotMappedToSA superfluous?
> 

Maybe.  Perhaps if the row status variable is "not in service"
you could get the error code to appear in the table.  However,
I believe your implementation is acceptable too.
-- 
Stuart Green
Nortel Networks - Arris Venture


> thanks,
> dan
> 
> > > > -----Original Message-----
> > > > From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> > > > Internet-Drafts@ietf.org
> > > > Sent: Friday, May 11, 2001 4:13 AM
> > > > To: IETF-Announce:; @ietf.org@manet
> > > > Cc: ipcdn@ietf.org
> > > > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >
> > > >
> > > > A New Internet-Draft is available from the on-line
> > > > Internet-Drafts directories.
> > > > This draft is a work item of the IP over Cable Data Network
> > > > Working Group of the IETF.
> > > >
> > > >       Title           : Management Information Base for DOCSIS
> > > > Cable Modems
> > > >                           and Cable Modem Termination Systems
> > > >
> > > >                           for Baseline Privacy Plus
> > > >       Author(s)       : S. Green
> > > >       Filename        : draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >       Pages           : 66
> > > >       Date            : 10-May-01
> > > >
> > > > This memo defines a portion of the Management Information Base (MIB)
> > > > for use with network management protocols in the Internet community.
> > > > In particular, it defines a set of managed objects for SNMP-based
> > > > management of the Baseline Privacy Plus features [17] of
> > > > DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> > > > Systems.
> > > > This memo specifies a MIB module in a manner that is compliant to the
> > > > SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> > > > SNMP framework and existing SNMP standards.
> > > > This memo is a product of the IPCDN working group within the Internet
> > > > Engineering Task Force.  Comments are solicited and should be
> > > > addressed to the working group's mailing list at ipcdn@terayon.com
> > > > and/or the authors.
> > > >
> > > > A URL for this Internet-Draft is:
> > > >
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >
> > > > Internet-Drafts are also available by anonymous FTP. Login with
> > > > the username
> > > > "anonymous" and a password of your e-mail address. After logging in,
> > > > type "cd internet-drafts" and then
> > > >       "get draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > > >
> > > > A list of Internet-Drafts directories can be found in
> > > > http://www.ietf.org/shadow.html
> > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > >
> > > >
> > > > Internet-Drafts can also be obtained by e-mail.
> > > >
> > > > Send a message to:
> > > >       mailserv@ietf.org.
> > > > In the body type:
> > > >       "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > > >
> > > > NOTE: The mail server at ietf.org can return the document in
> > > >       MIME-encoded form by using the "mpack" utility.  To use this
> > > >       feature, insert the command "ENCODING mime" before the "FILE"
> > > >       command.  To decode the response(s), you will need "munpack" or
> > > >       a MIME-compliant mail reader.  Different MIME-compliant
> > mail readers
> > > >       exhibit different behavior, especially when dealing with
> > > >       "multipart" MIME messages (i.e. documents which have been split
> > > >       up into multiple messages), so check your local documentation on
> > > >       how to manipulate these messages.
> > > >
> > > >
> > > > Below is the data which will enable a MIME compliant mail reader
> > > > implementation to automatically retrieve the ASCII version of the
> > > > Internet-Draft.
> > > >
> > >
> > > _______________________________________________
> > > IPCDN mailing list
> > > IPCDN@ietf.org
> > > http://www1.ietf.org/mailman/listinfo/ipcdn
> >


From ipcdn-admin@ietf.org  Mon May 21 11:27:01 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11152;
	Mon, 21 May 2001 11:27:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11570;
	Mon, 21 May 2001 11:22:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA25857
	for <ipcdn@ns.ietf.org>; Fri, 18 May 2001 20:36:38 -0400 (EDT)
Received: from ne.arris-i.com ([206.135.68.101])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20504
	for <ipcdn@ietf.org>; Fri, 18 May 2001 20:36:25 -0400 (EDT)
Received: from ne.arris-i.com (belafonte.ne.arris-i.com [141.251.36.84])
	by ne.arris-i.com (8.11.2/9.0.0) with ESMTP id f4J0c9s27815;
	Fri, 18 May 2001 20:38:10 -0400 (EDT)
Message-ID: <3B05BE27.FCF39418@ne.arris-i.com>
Date: Fri, 18 May 2001 20:28:23 -0400
From: Stuart Green <stu.green@ne.arris-i.com>
Organization: Nortel Networks - Arris Venture
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Hegglin <dhegglin@riverstonenet.com>
CC: ipcdn@ietf.org, ipcdn@terayon.com
Subject: Re: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
References: <002501c0de66$ee4b5a00$0353870a@DHEGGLINLAPTOP>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org
Content-Transfer-Encoding: 7bit

Daniel Hegglin wrote:
> 
> Stuart,
> 
> > > 1. The docsBpi2CmtsIpMulticastTable now has information in it that is
> > > redundant with the TEK table, specifically:
> > > - DataEncryptAlg
> > > - DataAuthentAlg
> > > - SAType
> > > Is there a reason these variables were added to the table?
> > >
> >
> > If a CMTS implements "create access" for a new multicast SAID,
> > these 3 fields need to be specified.
> 
> Hmmm, I agree on the dataEncryptAlg & dataAuthentAlg, but why the SAType?
> Is it ok if I set the type to be primary if the SAId is in the multicast
> range?  I guess there's other places in the spec where the operator can set
> unreasonable values.

The table is meant to be general purpose as it is difficult to predict
exactly how multicast services will be rolled out.  Your specific 
implementation may choose not to allow multicast mapping to primary
SAIDs.


> 
> I'm also a bit confused on the static/dynamic designation.  If I statically
> define a multicast mapping and define a static entry in the multicast
> authorization table for modem x, that makes it a static entry.  However, if
> modem y sends a SAMap requesting this mapping, it is technically a dynamic
> mapping for modem y, but the designation still stays static.  There are
> other scenarios like this, but to me it's not very clear from the spec since
> it can be static to one modem and dynamic to another.  My approach has been
> to declare any entry static if there are entries statically defined in the
> multicast authorization table using SNMP, even if this occurs after it is
> already designated dynamic through a SAMap request.  Is this the proper
> approach?

Yes I believe your implementation is acceptable and the static/dynamic
designation is arbitrary for BPI+.  


> 
> > > 3. When a CM requests a mapping for a multicast IP address that does NOT
> > > exist, we send the CM the appropriate reject message.  The
> > problem is that
> > > we don't have an entry in this table if there is no mapping, hance the
> > > SAMapRejectErrorCode can never be set to
> > noAuthForRequestedDSFlow(9), making
> > > it superfluous.  Am I missing something?
> 
> Whoops, my bad.  What I meant is dsFlowNotMappedToSA(10).  If there is no
> mapping then there is no entry in this table.  If there is no entry in this
> table, then we can never set this to 10.  If there is a mapping, then we
> would never set it to 10.  Does this make dsFlowNotMappedToSA superfluous?
> 

Maybe.  Perhaps if the row status variable is "not in service"
you could get the error code to appear in the table.  However,
I believe your implementation is acceptable too.
-- 
Stuart Green
Nortel Networks - Arris Venture


> thanks,
> dan
> 
> > > > -----Original Message-----
> > > > From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org]On Behalf Of
> > > > Internet-Drafts@ietf.org
> > > > Sent: Friday, May 11, 2001 4:13 AM
> > > > To: IETF-Announce:; @ietf.org@manet
> > > > Cc: ipcdn@ietf.org
> > > > Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >
> > > >
> > > > A New Internet-Draft is available from the on-line
> > > > Internet-Drafts directories.
> > > > This draft is a work item of the IP over Cable Data Network
> > > > Working Group of the IETF.
> > > >
> > > >       Title           : Management Information Base for DOCSIS
> > > > Cable Modems
> > > >                           and Cable Modem Termination Systems
> > > >
> > > >                           for Baseline Privacy Plus
> > > >       Author(s)       : S. Green
> > > >       Filename        : draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >       Pages           : 66
> > > >       Date            : 10-May-01
> > > >
> > > > This memo defines a portion of the Management Information Base (MIB)
> > > > for use with network management protocols in the Internet community.
> > > > In particular, it defines a set of managed objects for SNMP-based
> > > > management of the Baseline Privacy Plus features [17] of
> > > > DOCSIS1.1-compliant[16] Cable Modems and Cable Modem Termination
> > > > Systems.
> > > > This memo specifies a MIB module in a manner that is compliant to the
> > > > SNMP SMIv2 [5][6][7].  The set of objects are consistent with the
> > > > SNMP framework and existing SNMP standards.
> > > > This memo is a product of the IPCDN working group within the Internet
> > > > Engineering Task Force.  Comments are solicited and should be
> > > > addressed to the working group's mailing list at ipcdn@terayon.com
> > > > and/or the authors.
> > > >
> > > > A URL for this Internet-Draft is:
> > > >
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt
> > > >
> > > > Internet-Drafts are also available by anonymous FTP. Login with
> > > > the username
> > > > "anonymous" and a password of your e-mail address. After logging in,
> > > > type "cd internet-drafts" and then
> > > >       "get draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > > >
> > > > A list of Internet-Drafts directories can be found in
> > > > http://www.ietf.org/shadow.html
> > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > >
> > > >
> > > > Internet-Drafts can also be obtained by e-mail.
> > > >
> > > > Send a message to:
> > > >       mailserv@ietf.org.
> > > > In the body type:
> > > >       "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-05.txt".
> > > >
> > > > NOTE: The mail server at ietf.org can return the document in
> > > >       MIME-encoded form by using the "mpack" utility.  To use this
> > > >       feature, insert the command "ENCODING mime" before the "FILE"
> > > >       command.  To decode the response(s), you will need "munpack" or
> > > >       a MIME-compliant mail reader.  Different MIME-compliant
> > mail readers
> > > >       exhibit different behavior, especially when dealing with
> > > >       "multipart" MIME messages (i.e. documents which have been split
> > > >       up into multiple messages), so check your local documentation on
> > > >       how to manipulate these messages.
> > > >
> > > >
> > > > Below is the data which will enable a MIME compliant mail reader
> > > > implementation to automatically retrieve the ASCII version of the
> > > > Internet-Draft.
> > > >
> > >
> > > _______________________________________________
> > > IPCDN mailing list
> > > IPCDN@ietf.org
> > > http://www1.ietf.org/mailman/listinfo/ipcdn
> >


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


From ipcdn-admin@ietf.org  Tue May 22 15:20:34 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA01642;
	Tue, 22 May 2001 15:20:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA22975;
	Tue, 22 May 2001 15:19:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA22956
	for <ipcdn@ns.ietf.org>; Tue, 22 May 2001 15:19:07 -0400 (EDT)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA01577
	for <ipcdn@ietf.org>; Tue, 22 May 2001 15:18:49 -0400 (EDT)
Received: from srvmail.cablelabs.com (srvmail.cablelabs.com [10.5.0.15])
	by ondar.cablelabs.com (8.10.1/8.10.1) with ESMTP id f4MJF4122520;
	Tue, 22 May 2001 13:15:04 -0600 (MDT)
Received: by srvmail.cablelabs.com with Internet Mail Service (5.5.2653.19)
	id <L3FK08QT>; Tue, 22 May 2001 13:15:04 -0600
Message-ID: <4DF5E8A771ECD21187020008C7B1C5AF0139CE2A@srvmail.cablelabs.com>
From: Greg White <g.white@CableLabs.com>
To: "'Rich Woundy'" <rwoundy@cisco.com>,
        John Bradford Hart
	 <jbh@channelogics.com>
Cc: ipcdn@ietf.org
Subject: RE: [ipcdn] Re: docsQosPktClassTable
Date: Tue, 22 May 2001 13:15:03 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Approved: ondar
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org

I don't know if this is still a question or not, but one sentence in the text description in the qos-mib-05 (and possibly in earlier versions) is a little bit misleading.

From the qos-mib-05:
-----------------
The docsQosPktClassTable is distinct from the docsDevIpFilterTable of [21] in that docsQosPktClassTable is intended only to reflect the state of the dynamically added Service Flow Classifiers. SF Classifiers may be created only via a CM configuration file or from the Dynamic Service Addition (DSA) messages.  For this reason, docsQosPktClassTable is read-only.

The docsDevIpFilterTable is intended for external administration of packet classifiers.  See the section "Externally Administered Classification", below.
-----------------

The words "dynamically added" should probably be removed from the first sentence of the first paragraph.  The docsQosPktClassTable reflects the state of the SF Classifiers, regardless of whether they are statically provisioned (via CM config file) or dynamically added (via DSA or DSC message).  

What it doesn't reflect are any "Policy-based classifiers".  Those are described in the section "Externally Administered Classification", and involve the docDevIpFilterTable.

In other words, "statically-generated" and "externally administered" are two different things.

-Greg

-----Original Message-----
From: Rich Woundy [mailto:rwoundy@cisco.com]
Sent: Tuesday, March 13, 2001 12:39 PM
To: John Bradford Hart
Cc: ipcdn@ietf.org
Subject: [ipcdn] Re: docsQosPktClassTable


At 02:14 PM 3/13/2001 -0500, John Bradford Hart wrote:
>Rich,
>
>Thank you for getting back to me on this.  I am working with the
>intricacies of DOCSIS so these variations can get confusing.
>
>If I may ask another question. . .if the docsQosPktClassTable is "intended
>only to reflect the state of the dynamically added Service Flow
>Classifiers", then where are the statically-generated classifiers
>reflected?
>
>
>John

I believe they are reflected in docsDevFilterIpTable. My understanding is 
that "statically-generated" is equivalent to "externally administered" in 
the MIB.

See section 3 of the QoS MIB for a more complete explanation.

-- Rich


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

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


From ipcdn-admin@ietf.org  Fri May 25 19:19:03 2001
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27075;
	Fri, 25 May 2001 19:19:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA22959;
	Fri, 25 May 2001 19:01:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA22930
	for <ipcdn@ns.ietf.org>; Fri, 25 May 2001 19:01:31 -0400 (EDT)
Received: from ns.intelenet.net ([207.38.45.138])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26833
	for <ipcdn@ietf.org>; Fri, 25 May 2001 19:01:18 -0400 (EDT)
Received: from kbook (host198-111.cablelabs.com [192.160.73.198])
	by ns.intelenet.net (8.9.3/8.9.3) with SMTP id QAA04669;
	Fri, 25 May 2001 16:01:11 -0700 (PDT)
From: "Kaz Ozawa" <kaz@pobox.com>
To: "IETF Ipcdn" <ipcdn@ietf.org>,
        "DOCSIS OSS Mailing List" <docsis-oss@CableLabs.com>
Date: Fri, 25 May 2001 17:00:20 -0600
Message-ID: <NFBBJNDLELMELLPNJKCLCELKCHAA.kaz@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Content-Transfer-Encoding: 7bit
Subject: [ipcdn] BPI+ MIB docsBpi2Code...AccessStart Value
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org
Content-Transfer-Encoding: 7bit

The BPI+ spec, section D.3.2.2 specifies the codeAccessStart and 
cvcAccessStart as follows;

codeAccessStart: a 12-byte UTS time value referenced to GMT
cvcAccessStart: a 12-byte UTS time value referenced to GMT

In the BPI+ MIB, there are the following 4 objects related to 
these values.

docsBpi2CodeMfgCodeAccessStart
docsBpi2CodeMfgCvcAccessStart
docsBpi2CodeCoSignerCodeAccessStart
docsBpi2CodeCoSignerCvcAccessStart

These objects have the same description; ".... value referenced 
to Greenwich Mean Time (GMT)." Therefore, I don't think it make 
sense to put the non-zero time difference from the GMT in the 
9th through 11th octets (ex. -7:00). Therefore, I think it make 
sense to add the following sentence at the end of the description 
of these 4 objects.

"If the timezone information (9th-11th octets) is present, 10th 
octet (hours from UTC) must be zero and 11th octet (minutes from 
UTC) must be zero."

Note that the definition of DateAndTime is in RFC 1903.

Any comments?
Thanks,
kaz


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


