Mobile IPv4 Fast Handovers
draft-ietf-mip4-fmipv4-07
Yes
(Jari Arkko)
No Objection
(Chris Newman)
(Cullen Jennings)
(David Ward)
(Lisa Dusseault)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Tim Polk)
Note: This ballot was opened for revision 07 and is now closed.
Jari Arkko Former IESG member
(was Discuss, Yes, Discuss, Yes)
Yes
Yes
()
Unknown
Chris Newman Former IESG member
No Objection
No Objection
()
Unknown
Cullen Jennings Former IESG member
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
(2007-06-05)
Unknown
ABSTRACT: > Additional mechanisms may be defined in the > future versions of this document. Suggest to remove this sentence - this is being published now.
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
(2007-06-06)
Unknown
Gen-ART Review by Francis Dupont ...
Some editorial comments:
at page 6 section 4.2:
- in FA COA mode -> in FA-COA mode
- for the FSU field, I propose to add a MUST somewhere,
for instance: are used -> MUST be used
For each field: XXX field must be -> XXX field is
Throughout: Acknowledgement -> Acknowledgment
In Security Considerations, page 8, there is nothing about replay
attacks, i.e., how the "come back to where you was" attack is
handled? In IPv6 the protection is provided by IPsec with in the
good case anti-replay, is it done in IPv4?
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown