Framework for Generalized Multi-Protocol Label Switching (GMPLS)-based Control of Synchronous Digital Hierarchy/Synchronous Optical Networking (SDH/SONET) Networks
RFC 4257
Discuss
Yes
(Alex Zinin)
No Objection
(David Kessens)
(Margaret Cullen)
(Russ Housley)
(Sam Hartman)
(Ted Hardie)
No Record
Note: This ballot was opened for revision 05 and is now closed.
Harald Alvestrand Former IESG member
Discuss
Discuss
[Treat as non-blocking comment]
(2004-12-16)
Unknown
Reviewed by Elwyn Davies, Gen-ART, who found the presentation of materials somewhat suboptimal - in particular, he found conclusions and tutorial/background materials so thoroughly mixed that it's hard to tell what the document is trying to say. I'd like (at minimum) a response to the review before approving it.
Alex Zinin Former IESG member
Yes
Yes
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
(2005-04-21)
Unknown
After discussion with the AD I have cleared Harald's DISCUSS, even though the main point raised by Elwyn Davies, the Gen-Art reviewer, (excessive tutorial, unevenness of detail, whether it really is a framework and failure to highlight conclusions/requirements) has not been fixed. This is a judgement call. However, there is one new review comment that should be fixed editorially. > One additional point which I didn't pick up on in the previous review is a > 'red rag' issue in the second paragraph of 1.1: equating MPLS LSP in > general with circuit.
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
(2004-12-14)
Unknown
Missing IANA Considerations. I'm not sure I agree with the statements in the Security Considerations section about the need for GMPLS protocol specifications alone to identify and address security issues specific to protocol. If this document is describing an extension framework, shouldn't it also address the security implications of extensions in general? I'll leave it to Russ or Sam to determine if this merits a discuss or not.
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Record
No Record
(2004-12-16)
Unknown
Since this is a lot about SONET/SDH, would it not be good to have the document reviewed by someone from ITU-T as well?