Network Mobility Support Terminology
RFC 4885
Yes
(Jari Arkko)
No Objection
Lars Eggert
(Brian Carpenter)
(Cullen Jennings)
(Dan Romascanu)
(David Kessens)
(Lisa Dusseault)
(Magnus Westerlund)
(Ross Callon)
(Russ Housley)
(Ted Hardie)
Note: This ballot was opened for revision 06 and is now closed.
Lars Eggert
No Objection
Jari Arkko Former IESG member
Yes
Yes
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
Cullen Jennings Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
(2006-11-30)
Unknown
I understand acronym conflicts are hard to avoid, but "CE" seems a particularly annoying one as it is commonly referred to as "Customer Equipment" in the other half of the int-area. Given that "Entity" isn't a really descriptive term anyway, perhaps something else could be chosen? "CNR" for "Correspondent Node or Router" perhaps (this happens to encode that it can be either a CR and CN as well, which may be considered convenient)? 2.10. Correspondent Entity (CE) Refers to the entity which a Mobile Router or Mobile Network Node attempts to establish a Route Optimization session with. Depending on the Route Optimization approach, the Correspondent Entity maybe a Correspondent Node or Correspondent Router (see also NEMO Route Optimization in Section 7.5)
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown