Network Mobility Support Terminology
draft-ietf-nemo-terminology-06

Note: This ballot was opened for revision 06 and is now closed.

Lars Eggert No Objection

(Jari Arkko; former steering group member) Yes

(Brian Carpenter; former steering group member) No Objection

(Cullen Jennings; former steering group member) No Objection

(Dan Romascanu; former steering group member) No Objection

(David Kessens; former steering group member) No Objection

(Lisa Dusseault; former steering group member) No Objection

(Magnus Westerlund; former steering group member) No Objection

(Mark Townsley; former steering group member) No Objection

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 steering group member) No Objection

(Russ Housley; former steering group member) No Objection

(Ted Hardie; former steering group member) No Objection