Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)
draft-ietf-dmm-hnprenum-07
Yes
(Suresh Krishnan)
No Objection
(Adam Roach)
(Alia Atlas)
(Jari Arkko)
(Joel Jaeggli)
(Spencer Dawkins)
(Terry Manderson)
Note: This ballot was opened for revision 06 and is now closed.
Suresh Krishnan Former IESG member
Yes
Yes
(for -06)
Unknown
Adam Roach Former IESG member
No Objection
No Objection
()
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(for -06)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(2017-02-28 for -06)
Unknown
In the abstract, I would suggest s/as an update of the PMIPv6 specification./as an optional extension of the PMIPv6 specification./ to be crystal clear that this is not a formal update.
Ben Campbell Former IESG member
No Objection
No Objection
(2017-03-01 for -06)
Unknown
A couple of editorial comments: - Abstract: The last sentence is convoluted; please consider simplifying it. -3, first paragraph: "... the LMA has to notify a new HNP to a MAG...": Does this mean the same as "LMA has to notify a MAG about a new HNP"? If so, I think the text as written has the wrong direct object for "notify".
Deborah Brungard Former IESG member
No Objection
No Objection
(2017-02-28 for -06)
Unknown
Agree with Mirja's comment, it would be clearer if use normative language.
Jari Arkko Former IESG member
No Objection
No Objection
(for -06)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -06)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(2017-03-01 for -06)
Unknown
I agree with Stephen's discuss point.
Mirja Kühlewind Former IESG member
No Objection
No Objection
(2017-02-28 for -06)
Unknown
This document has a 2119 boilerplate but doesn't use normative language. I think it would actually be good to use normative language! Minor questions: - secion 4: "This temporary binding should only be used for the downwards packet transmission" By downward you mean 'to the MN', right? Why is this? Does that actually help in any scenario? - I'm not sure why section 3 is titled 'PMIPv6 Extensions'...?
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -06)
Unknown
Stephen Farrell Former IESG member
(was Discuss)
No Objection
No Objection
(2017-03-02 for -06)
Unknown
Section 7 says: "The protection of UPN and UPA messages in this document follows [RFC5213] and [RFC7077]." I'm not clear if "follows" means the same as "MUST be protected using end-to-end security association(s) offering integrity and data origin authentication" (RFC5213, section 4). I think it ought really, as otherwise this could subvert the security of PMIPv6. So wouldn't it make sense to be explicit that these new messages have the same MUST requirements as binding updates. Doing that by repeating the quoted text from 5213 would be a fine way to do that, but there may be better options. The above was a discuss ballot. The AD and an author agreed with the interpretation above that that adding a clarification might be good so I've cleared the discuss assuming they'll do that nicely. (Thanks). OLD COMMENT below - It might also be worth saying in section 7 that to provision a new HNP someone has to have setup all the IPsec stuff for that.
Terry Manderson Former IESG member
No Objection
No Objection
(for -06)
Unknown