All,
I have completed my AD evaluation of
draft-ietf-multimob-handover-optimization and found it to be quite
readable. Thank you.
I have a few issues that I would like to see resolved prior to
requesting IETF Last Call for this document. Feel free to discuss them
with me if clarifications are needed.
1. Introduction:
* In the 2nd paragraph, I don't see the benefit to referencing a draft
that has been expired for 3 years. I would suggest dropping the reference.
* In the 3rd paragraph : s/can help mitigating/can help mitigate
* The last paragraph is not needed and can be deleted.
2. Several places in the beginning of the document, there are references
to RFC 2710 but not RFC 3810. RFC 6224 uses both and section 4.1.1
explicitly discusses RFC 3810 (albeit indirectly as MLDv2). I would
suggest referencing both, add 3810 to the Normative References, and
properly reference 3810 in the appropriate places in section 4.
3. The reference to draft-ietf-multimob-pmipv6-ropt can be updated to be
RFC 7028.
4. Section 1.1
* The 2nd requirement is not a protocol requirement and should be
deleted. It is trying to mandate implementation/deployment behavior.
* The "on" in requirement 3 can be removed.
* Would it make sense to add an additional requirement that this
experimental approach not impact deployments of legacy implementations
of RFC 5213 and RFC 6224?
5. Section 4.1.2 : It would be clearer if the description of the message
formats that are borrowed from 2710 and 3810 refer to those formats by
the terms used in the RFC. For example, the Multicast Membership
Context field should refer to (or be called) the Multicast Address
Record (from 3810).
6. Sections 4.3.1.2 and 4.3.2.2
* Why are the sequence numbers 8-bit fields? The sequence fields in
other PMIPv6 messages are 16-bit.
* I would suggest adding references for the options allowed in these
messages (Mobile Node Identifier, Home Network Prefix, and Active
Multicast Subscription).
Regards,
Brian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ multimob mailing list [email protected] https://www.ietf.org/mailman/listinfo/multimob
