From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vYrMB1xgCIJ6TzxeeVZGN3RQo3r73YH4m3U3gZkMeX4=; b=mtHvvDJBI+67K/Y81aVfGHa3xLHB1SfeR5VP6d1Ho+LCwol30+V5o5JWgdus5CE/qr WhIxCzImkVApI4jsK1p34X3IopkKLhCC3Uy9S314o4BtNLt1yUrEBTS1fTltEzUMwrba fy3qPJcnWoWqrV2uY+fGzPHrqsYS5Tu06UpmCeWFb7uFgUvLCEU5HWxVt5+O39PK61H9 FipWtiPGv47FQdQfdp4EpQ2hS351doZV/jPc6qKFZSL5/oTDsANDLmQxMv1vqsUbitEL iwJGtcXItnFtGtjutaBQh8oZaWR6sDnTEmfJVUPT4wWDi1L+6I3vSLza1lkAiJxdwuXN ADYA== MIME-Version: 1.0 In-Reply-To: <54C79494.20402@gmail.com> References: <54C65044.7030501@gmail.com> <54C79494.20402@gmail.com> From: Ira McDonald Date: Tue, 27 Jan 2015 11:01:57 -0500 Message-ID: Content-Type: multipart/alternative; boundary=f46d043895770e286f050da461ea Subject: Re: [Printing-architecture] Projects for GSoC 2015: Implementing PWG standards List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Till Kamppeter , Ira McDonald Cc: "printing-architecture@lists.linux-foundation.org" --f46d043895770e286f050da461ea Content-Type: text/plain; charset=UTF-8 Hi Till, I'm not sure that there are recent IPP standards that are suitable for GSoC 2015 projects. I have reservations about SANE, because it competes with new IPP Scan Service, but doesn't add any value (that I can see). IPP Everywhere self-certification is moving forward, but slower than we all hoped. IPP Finishings 2.0, IPP FaxOut, IPP Scan are all good technology, but much too new to be widely deployed in shipping printers. IPP MSN 2.0 (Media Standardized Names) does do important extensions to media properties that would be worth reflecting in client print UIs, but it might be hard to get a student excited about more complete and accurate media properties. IPP JPS3 (Job and Printer Extensions Set 3) is full of good stuff - high value new attributes include "ipp-features-supported", "job-contraints-supported", "media-source-supported", "preferred-attributes-supported", "printer-geo-location", "printer-get-attributes-supported", "printer-icons", "printer-mandatory-job-attributes", and "printer-supply". Many of these are required by the subsequent IPP Everywhere spec, but it's IPP Everywhere that will be the impetus for widespread adoption, I think. We should talk about GSoC 2015 more after next week's PWG F2F meeting. Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto: blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Jan 27, 2015 at 8:37 AM, Till Kamppeter wrote: > On 27.01.2015 10:53, Michael Sweet wrote: > >> Ira, >> >> On Jan 26, 2015, at 8:59 PM, Ira McDonald >>> wrote: >>> ... >>> The IPP standard for uploading firmware will only be in the >>> work-in-progress >>> IPP System Service (milestone of Q3/Q4 2015 for Prototype draft). >>> Actually doing >>> the reboot to the new firmware is currently just an idea of mine for a >>> new operation >>> in IPP System Service. >>> >> >> There are a lot of security issues to address with firmware updates, and >> we'll need widespread adoption to make this useful. On the consumer end of >> printers, most now offer updates via their control panels and/or web >> interfaces, and on the high end you need a service engineer to apply the >> update. >> >> In any case, I don't see this as a GSoC 2015 project (2016?) >> >> > OK, so my suggestions (1) and (3) are not (yet) suitable for a GSoC > project. > > WDYT about my suggestion (2), the SANE drier for IPP network scanners? Is > the standard already in a usable state? Are there already MF devices with > standard-conforming scanners? > > Ira, what were your ideas of implementing PWG standards in GSoC projects? > > Till > > > --f46d043895770e286f050da461ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Till,

I'm not sure that there are recent IPP standards that a= re suitable for GSoC 2015
projects.

I have reservations about SAN= E, because it competes with new IPP Scan Service,
but doesn't add an= y value (that I can see).

IPP Everywhere self-certification is movin= g forward, but slower than we all hoped.

IPP Finishings 2.0, IPP Fax= Out, IPP Scan are all good technology, but much too
new to be widely dep= loyed in shipping printers.

IPP MSN 2.0 (Media Standardized Names) d= oes do important extensions to media properties that would be worth reflect= ing in client print UIs, but it might be hard to get
a student excited = about more complete and accurate media properties.

IPP JPS3 (Job and= Printer Extensions Set 3) is full of good stuff - high value
new attrib= utes include "ipp-features-supported", "job-contraints-suppo= rted",
"media-source-supported", "preferred-attribut= es-supported",
"printer-geo-location", "printer-get= -attributes-supported", "printer-icons",
"printer-ma= ndatory-job-attributes", and "printer-supply".=C2=A0 Many of= these are
required by the subsequent IPP Everywhere spec, but it's = IPP Everywhere
that will be the impetus for widespread adoption, I think= .

We should talk about GSoC 2015 more after next week's PWG F2F = meeting.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect= )
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundati= on Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Ch= air - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert= - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailt= o: blueroofmus= ic@gmail.com
Winter=C2=A0 579 Park Place=C2=A0 Saline, MI=C2=A0 4817= 6=C2=A0 734-944-0094
Summer=C2=A0 PO Box 221=C2=A0 Grand Marais, MI 4983= 9=C2=A0 906-494-2434


On Tue, Jan 27, 2015 at 8:37 AM, Till Kamppe= ter <till.kamppeter@gmail.com> wrote:
On 27.01.2015 10:53, Michael S= weet wrote:
Ira,

On Jan 26, 2015, at 8:59 PM, Ira McDonald <blueroofmusic@gmail.com> wrote:
...
<ira> The IPP standard for uploading firmware will only be in the wor= k-in-progress
IPP System Service (milestone of Q3/Q4 2015 for Prototype draft).=C2=A0 =C2= =A0Actually doing
the reboot to the new firmware is currently just an idea of mine for a new = operation
in IPP System Service.

There are a lot of security issues to address with firmware updates, and we= 'll need widespread adoption to make this useful.=C2=A0 On the consumer= end of printers, most now offer updates via their control panels and/or we= b interfaces, and on the high end you need a service engineer to apply the = update.

In any case, I don't see this as a GSoC 2015 project (2016?)


OK, so my suggestions (1) and (3) are not (yet) suitable for a GSoC project= .

WDYT about my suggestion (2), the SANE drier for IPP network scanners? Is t= he standard already in a usable state? Are there already MF devices with st= andard-conforming scanners?

Ira, what were your ideas of implementing PWG standards in GSoC projects?
=C2=A0 =C2=A0Till



--f46d043895770e286f050da461ea--