Information Model for Describing Network Device QoS Datapath Mechanisms
draft-ietf-policy-qos-device-info-model-10
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2004-01-08
|
10 | (System) | Ballot has been issued |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Russ Housley |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Alex Zinin |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Ned Freed |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Steven Bellovin |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, Yes, has been recorded for Bert Wijnen |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Thomas Narten |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, Discuss, has been recorded for Allison Mankin |
2004-01-08
|
10 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand |
2004-01-08
|
10 | (System) | Created "Approve" ballot |
2003-08-18
|
10 | Natalia Syracuse | State Changes to RFC Ed Queue from Approved-announcement sent by Natalia Syracuse |
2003-08-14
|
10 | Michael Lee | IESG state changed to Approved-announcement sent |
2003-08-14
|
10 | Michael Lee | IESG has approved the document |
2003-08-14
|
10 | (System) | Ballot writeup text was added |
2003-08-14
|
10 | (System) | Last call text was added |
2003-08-14
|
10 | (System) | Ballot approval text was added |
2003-08-11
|
10 | Michael Lee | Removed from agenda for telechat - 2003-08-07 by Michael Lee |
2003-08-08
|
10 | Bert Wijnen | Seems that doc is now approved with following RFC-Editor notes. I am checking for final go ahead from authors, wg chairs and involved ADs. RFC-Editor … Seems that doc is now approved with following RFC-Editor notes. I am checking for final go ahead from authors, wg chairs and involved ADs. RFC-Editor notes: - 2nd para of abstract OLD: This documenthis document NEW: This document - Page 2, 7th sentence OLD: Together, these two drafts NEW: Together, these two documents - Page 5, 1st para OLD: Together, these two drafts NEW: Together, these two documents - Page 5, 2nd para OLD: A separate draft could be written NEW: A separate document could be written - The word "draft occurs at several more places. It is best to change those all to "document". - Section 7 OLD: Like [PCIM} and {PCiME}, NEW: Like [PCIM] and [PCiME], - Co-Author Walter Weiss is now at: walterweiss@attbi.com |
2003-08-08
|
10 | Bert Wijnen | Status date has been changed to 2003-08-08 from 2003-08-01 |
2003-08-01
|
10 | Bert Wijnen | Status date has been changed to 2003-08-01 from 2003-07-03 |
2003-08-01
|
10 | Bert Wijnen | Placed on agenda for telechat - 2003-08-07 by Bert Wijnen |
2003-07-10
|
10 | Amy Vezza | State Changes to IESG Evaluation :: AD Followup from IESG Evaluation by Vezza, Amy |
2003-07-03
|
10 | Bert Wijnen | State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Wijnen, Bert |
2003-07-03
|
10 | Bert Wijnen | State Changes to Waiting for AD Go-Ahead from Waiting for Writeup by Wijnen, Bert |
2003-07-03
|
10 | Bert Wijnen | No IETF Last Call comments have been received. Document is on IESG agenda for July 10th. |
2003-07-03
|
10 | Bert Wijnen | Status date has been changed to 2003-07-03 from 2003-06-17 |
2003-07-03
|
10 | Bert Wijnen | State Changes to Waiting for Writeup from In Last Call by Wijnen, Bert |
2003-06-03
|
10 | Amy Vezza | Status date has been changed to 2003-06-17 from 2004-06-03 |
2003-06-03
|
10 | Amy Vezza | State Changes to In Last Call from Last Call Requested by Vezza, Amy |
2003-06-03
|
10 | Bert Wijnen | WG chair gave me a go ahead. |
2003-06-03
|
10 | Bert Wijnen | State Changes to Last Call Requested from AD Evaluation :: AD Followup by Wijnen, Bert |
2003-06-03
|
10 | Bert Wijnen | AD is OK with new rev. Checking with WG chairs if they believe WG has consensus with this revision. |
2003-06-03
|
10 | Bert Wijnen | Status date has been changed to 2004-06-03 from 2004-05-07 |
2003-06-03
|
10 | Bert Wijnen | Revision 9 had inadvertent changes included by the editor. So a new revision 10 was needed. Revison 10 was received on May 27th. |
2003-06-03
|
10 | Bert Wijnen | State Changes to AD Evaluation :: AD Followup from AD Evaluation :: Revised ID Needed by Wijnen, Bert |
2003-06-03
|
10 | (System) | Last call sent |
2003-05-27
|
10 | (System) | New version available: draft-ietf-policy-qos-device-info-model-10.txt |
2003-05-19
|
09 | (System) | New version available: draft-ietf-policy-qos-device-info-model-09.txt |
2003-05-07
|
10 | Bert Wijnen | Bob Moore promised a new rev by May 11th. |
2003-05-07
|
10 | Bert Wijnen | Status date has been changed to 2004-05-07 from 2004-04-09 |
2003-05-07
|
10 | Bert Wijnen | State Changes to AD Evaluation :: Revised ID Needed from AD Evaluation by Wijnen, Bert |
2003-04-09
|
10 | Bert Wijnen | I also question the (current) wisdom of going standards track. Here is my posting to the WG list: -----Original Message----- From: Wijnen, Bert (Bert) Sent: … I also question the (current) wisdom of going standards track. Here is my posting to the WG list: -----Original Message----- From: Wijnen, Bert (Bert) Sent: woensdag 9 april 2003 19:04 To: Joel Halpern (E-mail); Ed Ellesson (E-mail) Cc: Randy Bush (E-mail); 'Policy@ietf.org' Subject: What to do with: draft-ietf-policy-qos-device-info-model-08.txt I have posted my AD review to the policy WG mailing list today. Last week Friday I posted my review of QPIM. I wonder... for both documents, but specifically for this one: Do we really want this (still) to be standards track. My reasoning: - We (or at least I) have seen interest in this space dimish (if not dissappear completely) - The document has a lot of places where it talks about more work that could be done, should be done, and how together with that work, this would be something good. Specifically a mapping to LDAP Schema . But as far as I know, we see not interest in that. Do we? And then, if no such docs will ever show up, what use do these docs then have? - I believe I saw some ( a little) interest expressed to do an LDAP Schema mapping. But not for QPIM and QDDIM, do I ? So maybe Informational or Experiemntal is better? Just thinking aloud here. Pls send me your comments. Thanks, Bert |
2003-04-09
|
10 | Bert Wijnen | -----Original Message----- From: Wijnen, Bert (Bert) Sent: woensdag 9 april 2003 18:38 To: 'policy@ietf.org' Subject: AD review of: draft-ietf-policy-qos-device-info-model-08.txt OK, here is my review … -----Original Message----- From: Wijnen, Bert (Bert) Sent: woensdag 9 april 2003 18:38 To: 'policy@ietf.org' Subject: AD review of: draft-ietf-policy-qos-device-info-model-08.txt OK, here is my review (finally... blush) - Needs to be checked against ID-NITS, see: http://www.ietf.org/ID-nits.html Also pls check against RFC2223bis see draft-rfc-editor-rfc2223bis-04.txt Things that fall under this category: - no citations in abstract - split references in normative and informative - expand Acronyms when used for the first time - use proper references in the references section - is the reference to cim 2.5 correct? - not sure if the IP address as on page 7 is allowed according to ID-NITs - I see some Msoft characters in the doc (page 12 and 64 are examples) - many referenced documents have become RFCs now. You may want to update those. - I suspect that security area is too weak. Specifically if you tell people to use IPSEC, you have to explain how that is done. But... maybe you can refer to PCIM and PCIMe, similar to how you did it for QPIM. Maybe there are some extra concerns since you also derive a lot directly from CIM ?? - In the abstract, I think that the last piece needs to be removed. That is: A separate draft could be written to provide a mapping of the data contained in this document to a form suitable for implementation in a directory that uses (L)DAP as its access protocol. Similarly, a draft could be written to provide a mapping of the data in [QPIM] to a directory. Together, these four drafts (information models and directory schema mappings) would then describe how to write QoS policy rules that can be used to store information in directories to configure device QoS mechanisms. Cause that tells what "could be done" but that cannot be the "abstract" for this document, can it? - The document speaks about "this draft" a lot. I think it should be changed throughout the document into "this document". So that once it is published we do not see "this draft" anymore. - Page 11. It might help if in the figure you indicate where we find CIM, PCIM, PCIMe, QPIM, QDDIM. etc - I see (as an example on page 16/17) QoSService as a class. Then the doc talks about the plural QoSServices, and I am not sure if it always means QoSService Instances or subclasses of QoSService. At other places it talks about "QoS services" which seems better to me - Page 17 I see: Note that this work is not yet completely aligned, as there are differences among the DiffServ Informal Management Model, the DiffServ MIB, the DiffServ PIB, and this draft. Work to finish aligning these drafts is in progress, and will be reflected in the next revision of this draft. Does this mean you were expecting a new rev of QDDIM anyway? Anyway, such text probably does not belong in a doc that goes for RFC publication. - AS an example: I see on page 21 Implementations may recognize other 's in addition to these. If collisions of implementation-specific 's become a problem, it is possible that 's may become an IANA- administered range in a future revision of this standard. This document itself should not claim that it is a standard. Or at least not in the text. If it gets approved as stds track then RFC-Editor will add that in the footing. I suggest to use "this document" instead of "this standard". Pls check if there are more occurences. - The figures on pages 26 to 32 are not consistent in their use of class names and such. I can understand that you need to abbreviate becuase of space constraints, but it might be good to do so in a consistent manner, and to list the abbreviations and explain which exact Class they represent. - On page 37 you claim (at top) that "is shown in figure 9" but I think it is actually figure 10. On page 38 it should be figure 11 instead of 10 (or so I think) - I am a bit surprised to see how the descriptions of Properties is done. In the PCIM (RFC3060) it was done pretty formal, for example: NAME CN DESCRIPTION A user-friendly name of a policy-related object. SYNTAX string Another one: NAME Mandatory DESCRIPTION A flag indicating that the evaluation of the PolicyConditions and execution of PolicyActions (if the condition list evaluates to TRUE) is required. SYNTAX boolean DEFAULT VALUE TRUE Or yet anbother one: NAME SequencedActions DESCRIPTION An enumeration indicating how to interpret the action ordering indicated via the PolicyActionInPolicyRule aggregation. SYNTAX uint16 VALUES mandatory(1), recommended(2), dontCare(3) DEFAULT VALUE dontCare(3) In RFC3460 I see it done in a similar way: NAME PolicyDecisionStrategy DESCRIPTION The evaluation method used for policies contained in the PolicySet. FirstMatching enforces the actions of the first rule that evaluates to TRUE; All Matching enforces the actions of all rules that evaluate to TRUE. SYNTAX uint16 VALUES 1 [FirstMatching], 2 [AllMatching] DEFAULT VALUE 1 [FirstMatching] So why is that not followed in this document? - Does Class TockenBucketMeterService not need a deltaInterval property? Otherwise what does the AverageRate property mean? - Do we still want/need a class TosMarkerService and a property of ToSValue? Has ToS not been obsoleted? - Class REDDropperService derives from DropperService. Does the ingeritedDropperType always have the value "Random" ?? - sect 4.3.21.2 does not even tell the datatype of the property - Sect 4.3.26 I am being told that the proper name for a flow label is FlowLabel and not FlowID. Not sure how serious this is. - Section 4.3.34 I do not see any of the properties described, do I? - sect 4.3.37.2 Would it not be better to use a 32bit unsigned? - sect 4.3.37.5 May I assume that the buffers are being shared? That is not so clear from the description (at least not to me). - Sect 4.3.40 Explain what WRR stands for - sect 4.3.40.1 Here I wonder if a 16 bit unsigned would not be more than sufficient Its units are "thousands" ?? Thousands of what? - sect 4.3.4.2 Does this property not add just extra complexity? Or is that just me thinking so? And... what happens if both WeightingFactor and Priority are equal? - Sect 4.4.18 and 4.4.19 Am I missing Property descriptions? - sec 4.4.28 Am I missing Property descriptions? Thanks, Bert |
2003-04-09
|
10 | Bert Wijnen | Status date has been changed to 2004-04-09 from 2002-05-06 |
2002-08-01
|
10 | Bert Wijnen | Changed Responsible field to "Responsible AD" so this doc will show up for me to handle. |
2002-08-01
|
10 | Bert Wijnen | responsible has been changed to Responsible AD from Area Directors |
2002-05-31
|
08 | (System) | New version available: draft-ietf-policy-qos-device-info-model-08.txt |
2002-05-03
|
10 | Bert Wijnen | Bert needs to do a AD review before requesting IETF Last Call. |
2002-05-03
|
10 | Bert Wijnen | responsible has been changed to Area Directors from Responsible AD |
2002-05-03
|
10 | Bert Wijnen | State Changes to AD Evaluation from New Version … State Changes to AD Evaluation from New Version Needed (WG/Author) by Bert Wijnen |
2002-05-02
|
10 | Jacqueline Hargest | Intended Status has been changed to Proposed Standard from None |
2002-05-02
|
10 | Jacqueline Hargest | Draft Added by Jacqueline Hargest |
2002-03-01
|
07 | (System) | New version available: draft-ietf-policy-qos-device-info-model-07.txt |
2001-11-27
|
06 | (System) | New version available: draft-ietf-policy-qos-device-info-model-06.txt |
2001-08-15
|
05 | (System) | New version available: draft-ietf-policy-qos-device-info-model-05.txt |
2001-06-08
|
04 | (System) | New version available: draft-ietf-policy-qos-device-info-model-04.txt |
2001-05-08
|
03 | (System) | New version available: draft-ietf-policy-qos-device-info-model-03.txt |
2000-11-29
|
02 | (System) | New version available: draft-ietf-policy-qos-device-info-model-02.txt |
2000-07-24
|
01 | (System) | New version available: draft-ietf-policy-qos-device-info-model-01.txt |
2000-04-10
|
00 | (System) | New version available: draft-ietf-policy-qos-device-info-model-00.txt |