Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)
RFC 5604

Note: This ballot was opened for revision 11 and is now closed.

(Mark Townsley) Yes

(Ron Bonica) No Objection

Comment (2008-07-02 for -)
No email
send info
support Dan's discuss

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

(Pasi Eronen) No Objection

Comment (2008-07-01 for -)
No email
send info
Editorial suggestions from Scott Kelly's SecDir review:
- I would suggest adding a sentence to the introduction which 
articulates the background the reader is assumed to have, for 
example, what RFCs they are expected to be conversant with, 
in order to understand the content of this document.
- TDM should be expanded with first use

(Cullen Jennings) No Objection

(Chris Newman) No Objection

(Jon Peterson) No Objection

(Tim Polk) No Objection

Comment (2008-07-01 for -)
No email
send info
As noted in Scott Kelly's secdir review and Dan's preliminary discuss, the replacement of
parentheses with double quotes is somewhat confusing.  Since Dan is already holding a discuss,
I am balloting NoObj but would like to note that I support Dan's position.

(Dan Romascanu) (was Discuss) No Objection

Comment (2008-07-02)
No email
send info
1. The introduction has text about comments to be made to the WG and the WG list. I believe that this text needs to be dropped, as the future RFC may be longer lived than the WG

2. In Section 3, s/[SATOP] draft/[SATOP]

3. Last paragraph in Section 3 uses RFC2119 keywords. I wonder whether this is appropriate, as the text describes terminology and functionality defined someplace else and not in this document, 

4. The procedure described in Section 7 ends with verifying that pwTDMConfigError returns no error. What actions are being taken by a manager and by the agent if there are errors reported in this object? Is the procedure repeated from start, from some place within the algorithm, do any entries need to be cleared and configured again? 

5. The document makes a non-consistent use of the UNITS clause - it is defined for some objects it is not for other. 

6. The DESCRIPTION clause of pwTDMValidDayIntervals defines the minimal value as 1. Why is then the syntax allowing for 0, is there any special significance?

(David Ward) No Objection

Magnus Westerlund No Objection