Network Mobility Support Terminology
RFC 4885

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

(Jari Arkko) Yes

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

(Ted Hardie) No Objection

(Russ Housley) No Objection

(Cullen Jennings) No Objection

(David Kessens) No Objection

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

Comment (2006-11-30)
No email
send info
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)

Magnus Westerlund No Objection