Hi,
>From here (Detroit area in Michigan), entire PWG site (HTTP and FTP) has
been down for several hours.
I can't reach the home page via HTTP. FTP connects, but an "ls" hangs
indefinitely and Control-C hangs
trying to break the connections.
So I can't fetch these files just now.
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/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto: blueroofmusic at gmail.com
Jan-April: 579 Park Place Saline, MI 48176 734-944-0094
May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434
On Mon, Mar 12, 2018 at 9:48 AM, Michael Sweet <msweet at apple.com> wrote:
> Smith,
>> Some quick feedback after looking at the new draft:
>> - Abstract: The wording here seems a little redundantly redundant. :)
>> - Sections 4.1.3 and 4.1.5: RFC updates - 7616 for Digest and 7617 for
> Basic.
>> - Section 4.1.6 (and this is probably an errata for IPP Scan and IPP INFRA
> as well): access-x509-certificate is insufficient by itself for
> authentication - you need the private key as well to do the signing (to
> prove that you "own" the certificate...) Probably need to say that the
> printer obtains the signing key through an out-of-band means.
>> - Section 5.1: Not sure how to use this attribute; we don't have its
> equivalent for IPP Scan or INFRA.
>> - I think we'll need to add an Additional Semantics section to briefly say
> that job-save-accesses gets copied to the Job Object but not returned as a
> Job attribute.
>> - Section 16: Should say more about protecting the values of
> job-save-accesses in transit and at rest.
>> Overall I think the draft is shaping up, although my gut says we still
> need to frame/document the scope and usage a little more - right now I can
> see how this would provide credentials for the save process but not how it
> requires those credentials for the reprint use case.
>>> > On Mar 11, 2018, at 11:24 PM, Kennedy, Smith (Wireless & Standards
> Architec) <smith.kennedy at hp.com> wrote:
> >
> > Greetings,
> >
> > I have just posted a new draft of IPP Job Save Password:
> >
> > https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-> savepassword-20180311.pdf
> > https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-> savepassword-20180311.odt
> > https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-> savepassword-20180311-rev.pdf
> > https://ftp.pwg.org/pub/pwg/ipp/whitepaper/tb-> savepassword-20180311-rev.odt
> >
> > This draft refactors the proposed attributes as per the discussion back
> in December 2017 and that we further briefly discussed at the February 2018
> F2F.
> >
> > Cheers,
> >
> > Smith
> >
> > /**
> > Smith Kennedy
> > Wireless & Standards Architect - IPG-PPS
> > Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC
> Forum / USB-IF
> > Chair, IEEE ISTO Printer Working Group
> > HP Inc.
> > */
> >
> >
> >
> > _______________________________________________
> > ipp mailing list
> > ipp at pwg.org> > https://www.pwg.org/mailman/listinfo/ipp>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20180312/4da85dc8/attachment.html>