North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Google wants to be your Internet

  • From: Brandon Galbraith
  • Date: Tue Jan 23 12:33:17 2007
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=DlNgCp1Pdix7pDQX3TDLHC/WA0Qw5Qrm+sAlSGZqlA4MiCXnKbLXLoUOQOfOdlp1I9yz/6S/7Ap64k/4o+NngdiIR3CwnF2nO1v/PVMSv+ZrRYoXTsQaSZuoHGkrW/wJ6NsO9aDPtuuh+UnTDDN+HxApgA7wAiL6RckcjEWeTss=
Why is IP required, and even if you used IP for transport why must the
meter identification be based on an IP address?  If meters only report
information, they don't need a unique transport address and could put
the meter identifier in the application data.

Even if the intent is to include additional controls, e.g. cycle air
conditioners during peak periods, you still don't need to use IP or
unique IP transport addresses.

Just because you have the hammer called IP, doesn't mean you must use
it on everything.

Exactly. A meter should be able to connect over an available transport method, and be identifiable via a serial number, not an IP. It may need to grab a DHCP address of some sort (or whatever the moniker is for the transport available), but in the end it's unique serial number should be used to identify itself.