Ira,
On May 10, 2012, at 1:30 PM, Ira McDonald wrote:
> Hi,
>> Thanks for the DEL catch James!
>> Mike - bullet (2) (MUST NOT accept/transfer controls except CR or LF)
> runs afoul of the ABNF for "ipp-printer-device-id" in [PWG5107.2] which
> also allows HT (per IEEE 1284 parent spec).
I have no problem adding HT as an allowed character. I am less inclined to allow VT mainly because I see it rarely and there is no "standard" vertical tab spacing as there is for HT (8 columns for most terminal emulators and web browsers). But even HT is problematic for display (less so for parsing and logging).
> And for attributes shared/coordinated w/ IETF or PWG MIBs, note that
> DisplayString (RFC 2579) allows NVT-ASCII per TELNET (RFC 853),
> which defines several control characters but allows *all* of the C0 control
> characters.
>> Examples of ASCII attributes include: sysDescr, sysName, sysLocation,
> sysContact, and hrDeviceDescr.
We can define how such values are mapped; realistically I think that we can simply state that any mapping of SNMP properties to IPP attributes MUST include filtering of control characters not allowed by the corresponding attribute type.
(and for things that *are* a direct mapping like prtAlert, prtMarkerSupply, etc. we use octetString which will remain unaffected...)
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20120510/7aa8fb10/attachment-0001.html>