Re: RFC: "printer-service-col (collection)" Printer Description
Michael Sweet via ipp <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Smith, We've traditionally left it wide open to allow for other communication methods besides email and telephone... > On Feb 24, 2021, at 6:38 PM, Kennedy, Smith (Wireless & IPP Standards) <[email protected]> wrote: > > +1 Using a collection is a good idea! > > In system service, the “printer-contact-col” attribute refers the reader to the “system-contact-col“ attribute. Its “contact-uri“ member attribute doesn’t currently constrain the range of allowable schemes. Do we want to do that or leave it wide open? > > Cheers, > Smith > --- > Smith Kennedy > [email protected] > > >> On Feb 23, 2021, at 9:03 AM, Michael Sweet via ipp <[email protected]> wrote: >> >> All, >> >> As part of our discussions during the last F2F, we determined that IPP should expose the Printer MIB's prtGeneralServicePerson element. The MIB definition is just an octet string, but in keeping with IPP System Service's "printer-contact-col" (prtGeneralCurrentOperator) I think we should convert it to a collection that can convey the name, email address, telephone number, and VCARD information. >> >> "printer-service-col (collection)" >> >> This Printer Description attribute contains the contact information for the individual or organization responsible for performing maintenance on the Printer. Member attributes are the same as the "printer-contact-col" Printer Description attribute [PWG5100.22]. >> >> Thoughts? >> >> ________________________ >> Michael Sweet >> >> >> >> _______________________________________________ >> ipp mailing list >> [email protected] >> https://www.pwg.org/mailman/listinfo/ipp ________________________ Michael Sweet _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp