This document is is nearly ready for publication as an Informational RFC.
Over all, this is quite readable and covers a lot of ground.
Moderate: Describing MPLS as a routing protocol seems wrong in at least
two regards:
1) MPLS control can be described as a path placement protocol. But is not
what we usually describe as a routing protocol.
2) The MPLS data plane which is necessary for the ETS work and which is
described by the paragraph is a packet forwarding behavior, not a routing
protocol.
Minor: The document would be helped by an early explicit definition of
"administrative domain". While this is actually included in [REQ], it
would be helpful if it was in this document, as the concept is so central
to the work.
Minor: IdNits indicates part of the 3978 / 3979 material is missing.
References: This document can not be understood with reference [REQ], and
therefore that reference should be normative.
----
A Framework for Supporting Emergency Telecommunications Services (ETS)
Within a Single Administrative Domain
draft-ietf-ieprep-domain-frame-05.txt
Token: Jon Peterson
Reviewer: Joel Halpern
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art