RE: draft-ietf-rap-feedback-fr-pib-05.txt submission

Kwok Ho Chan <[email protected]> Fri, 04 Apr 2003 11:16:54 -0500
Newsgroups gmane.ietf.rap
Message-ID <5.2.0.9.0.20030404111606.02e83030@zbl6c002.corpeast.baynetworks.com>
Bert and draft co-authors:
These changes are OK for me.
Thanks!
-- Kwok --

At 03:54 PM 4/4/03 +0200, Wijnen, Bert (Bert) wrote:
>Sorry that it took so long to re-review this.
>
>I am ready to take this to IESG if the WG is OK that I
>propose it for publication as Informational RFC.
>
>However,
>I would still suggest that we also rename the
>    FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN
>into
>    FRAMEWORK-FEEDBACK-PIB PIB-DEFINITIONS ::= BEGIN
>that seems much more inline with the whole module.
>
>I also need to have RFC2578, RFC2863 as Normative References,
>because you do IMPORT from those RFCs.
>
>To be fully compliant with latest Copy-right ploicy, the
>DESCRIPTION clause also needs a copyright statement,
>aka
>
>       DESCRIPTION
>               "The PIB module containing the base set of policy rule
>               classes that are required for support of all policy
>               usage  monitoring, tracking and reporting policies"
>
>Should become
>
>       DESCRIPTION
>               "The PIB module containing the base set of policy rule
>               classes that are required for support of all policy
>               usage  monitoring, tracking and reporting policies.
>
>               Copyright (C) The Internet Society (year). This version
>               of this PIB module is part of RFC xxxx; see the RFC
>               itself for full legal notices."
>
>See: http://www.rfc-editor.org/policy.html
>
>Further, in the IANA COnsiderations section, I would change:
>   This document describes the frwkFeedbackPib Policy Information Base
>   (PIB) module for standardization under the "pib" branch registered
>   with IANA. An IANA assigned PIB number is requested for this PIB
>   under the "pib" branch.
>Into:
>   This document describes the frwkFeedbackPib Policy Information Base
>   (PIB) module for registration under the "pib" branch registered
>   with IANA. The IANA has assigned PIB number TBD.
>
>While you're at it, you migth update the FRAMEWORK PIB reference to
>point to RFC3318. And to let FEEDBACKfWRK reference point to RFC3483.
>
>Let me know (asap) if the above is OK and if Martin can quickly
>spin a new revision.
>
>Thanks,
>Bert
>
> > -----Original Message-----
> > From: Bokaemper, Martin [mailto:[email protected]]
> > Sent: donderdag 19 december 2002 21:16
> > To: Rap-wg (E-mail)
> > Cc: 'Wijnen, Bert (Bert)'
> > Subject: FW: draft-ietf-rap-feedback-fr-pib-05.txt submission
> >
> >
> > Hello!
> >
> > A version of the draft with changes to address Berts comments
> > has just been submitted.
> > The changes:
> > - 'portion of Policy Information Base' change in Abstract
> > - REVISION and LAST-UPDATED clause updated & synced.
> > - Clarified DESCRIPTIONs for frwkFeedbackActionList,
> >   frwkFeedbackActionListTable, frwkFeedbackActionListTag
> >   and frwkFeedbackActionListRefID.
> > - added [RFC2119] reference
> > - updated DESCRIPTION of Usage64 objects to for initialization
> >   of Usage64.
> > - housekeeping ('Last Updated', 'Expiration' and TOC)
> >
> > Unchanged:
> > - Usage32/64 - see todays discussion on the list
> >
> > ciao,
> > Martin.
> >
> > -----Original Message-----
> > From: Bokaemper, Martin
> > Sent: Thursday, December 19, 2002 2:56 PM
> > To: '[email protected]'
> > Cc: 'Rawlins, Diana'; Bokaemper, Martin; 'Kwok Ho Chan (Kwok Ho Chan
> > [[email protected]])'; Hahn, Scott; 'Wijnen, Bert (Bert)';
> > Kulkarni, Amol; '[email protected]'
> > Subject: draft-ietf-rap-feedback-fr-pib-05.txt submission
> >
> >
> > I would like to submit an updated Internet Draft. This draft
> > is a work of
> > the Resource Allocation Protocol (RAP) WG. The details are as follows:
> >
> >        Title     :  Framework Policy Information Base for
> > Usage Feedback
> >        Filename  :  draft-ietf-rap-feedback-fr-pib-05.txt
> >
> > Please let me know if there are any problems.
> >
> > Thanks,
> > Martin.
> >
> >
> >