BoF Name: Internet Personal Appliance Control (IPAC) IETF Area: Internet Area Chairs: Simon Tsang Mauricio Arango Internet Area Director(s): Erik Nordmark Thomas Narten Conflicts to avoid (in order of importance): Zeroconf WG SIP WG IMPP WG Number of slots requested: 1 Length of slot requested: 1 hour Expected attendance: 50 Agenda: 5 minutes: Opening - Chairs: Overview of Agenda - Chairs: 'Why we are here' focus 10 mins: Discussion ID - Stan Moyer, Telcordia: draft-tsang-appliances-discuss-00 10 mins: Relationship of other industry/standards bodies to IPAC - Dave Marples, OSGi: OSGi - Alex Popoff, Microsoft: UPnP 10 mins: The need for IPAC - an Industrial Perspective - Ibrahim Kamel, Panasonic Research - TBA 20 mins: Open discussion - Chairs: Propose WG work items and charter - All: Open discussion on discussion ID, proposed charter and focus of work 5 mins: Closing - Chairs: Review work items highlighted. Propose charter for WG. Full description of BoF: The purpose of the Internet Personal Appliance Control (IPAC) BoF is to discuss the problem space surrounding IPAs, and to identify areas which will require work within the IETF. A key achievement would be to gain a general consensus on what part of the problem space would be most appropriate for study in the IETF. Short presentations from industry representatives and IPA manufacturers will aid general understanding of how the IETF relates with respect to other working groups and standards bodies, and help motiviate the need for an IPAC WG. Internet Personal Appliances (IPAs) may be considered to be simple, dedicated purpose, limited configuration, devices such as washing machines, refrigerators, lamps, and televisions as IPAs. Other devices such as personal computers (PCs), workstations, and personal digital assistants (PDAs) have much more general applicability and higher levels of configurability and are normally considered as computational devices. These would not meet the definition of an IPA. Devices such as Digital Cameras and MP3 players are in the ‘grey space’ between an IPA and general purpose device. Of course, there is no reason why general computation devices cannot use the capabilities that are defined for IPAs, but it is important to design for the IPA target. We consider that Internet Personal Appliances (IPAs) are networked devices which have the following characteristics: 1) Dedicated functionality with limited configurability and optimized user interface - an Internet connected Calculator might be considered an IPA, a Palm Pilot running a calculator application would not. 2) The ability to interact with the physical environment through sensors and actuators; thus, a Network Attached Storage (NAS) device would not be considered an IPA. 3) Limited (or restricted) general purpose computational power, though the devices may possess high-computation power for specific tasks such as image processing, or audio processing as in the case of an MP3 player. In general, IPAs will be devices with sensors and/or actuators with limited computational power, but they will always have some form of permanent or temporary network connectivity. IPAs may be portable and may provide service in multiple locations. Some may be mobile and may provide service while stationary or in transit. Note that these portability and mobility issues may introduce new constraints or novel operational modes for specific IPAs - a typical example might be a MP3 player capable of relaying an Internet Radio Station while stationary and network connected, but only being able to play cached content when mobile without any network connection. The Internet Draft draft-tsang-appliances-discuss-00 provides some initial discussion points on the IPAC problem space. A summary of these issues is provided below. 1. IPAC Overview 1.1. What Are Internet Personal Appliances (IPAs)? 1.2. Where Is the Intelligence? 1.3. How Do We Want to Interact with IPAs? 1.4. Where Will IPAs Be Found? 1.4.1 The Home Environment (HE) 1.4.2 Automobile Environment (AE) 1.4.3 Visited Domains 2. General Issues 2.1. Who Owns the IPA? 2.2. Information Privacy Issues 3. IPA Issues 3.1. Connectivity Issues 3.1.1 Network Connectivity 3.1.2 Issues With Thin and Fat IPAs 3.1.3 Intermittent Access 3.2. Security Issues 3.2.1 Trust Zones and Domains of Control 3.2.2 Authentication of IPAs 3.2.3 Privacy 3.3. Operational Issues 3.3.1 Configuration and Provisioning 3.3.2 Billing 3.3.3 Faults and Remote Diagnosis 3.3.4 Distributed Agreements 3.3.5 Restricted I/O 3.3.6 Multiplicity 3.3.7 Initial Deployment 3.3.8 Decomposition of IPAs 4. Relation to IETF Working Groups and Other Organizations