bytes on the wire, since the keyword name of the attribute is sent
on the wire.
So if we change from "printer-uri" to "printer-url", we are changing
the on the wire protocol too (as well as the model).
All the attributes affected would be:
Error status codes (editorial only):
There are a number of attributes whose data syntax is 'uri', but don't
have uri in their names, so we could either change these name
RFC 1630 has the following note on the first page:
Note that the work contained in this memo does not describe an
Internet standard. An Internet standard for general Resource
Identifiers is under development within the IETF.
</bigger>At 13:18 04/06/1998 PDT, Paul Moore wrote:
> URI The URI draft has not matured to the standards
>track. There are some
> serious problems to resolve, which may take
> time. The
> advice from Larry Masinter, who is the editor, seems
>to be to go
> back to using URL where ever we use URI (which would
> mean changing a number of
> attribute names!).
>Which changes the wire representation! This is not just a
>> -----Original Message-----
>> From: Carl-Uno Manros [SMTP:firstname.lastname@example.org]
>> Sent: Monday, April 06, 1998 10:57 AM
>> To: email@example.com
>> Subject: IPP> ADM - Trouble with references
>> One of the things I discovered during last week's IETF meeting in LA
>> that we are in trouble with a couple of our references in the IPP
>> This means that even if we get past the IESG review, we will have
>> when documents arrive at the RFC editor's desk.
>> Here are the problem children:
>> RFC2234 ABNF, although this is an RFC officially on the standards
>> Dave Crocker who is the editor, indicated that there are
>> a couple of minor
>> changes to fix. He will do those ASAP.
>> TLS TLS has been accepted by the IESG, but they have a reference
>> with PKIX, which still has to be resolved. The quick
>> be to change
>> to X.509 as reference. The editors are working on
>> this change.
>> URI The URI draft has not matured to the standards track. There
>> are some
>> serious problems to resolve, which may take
>> time. The
>> advice from Larry Masinter, who is the editor, seems to
>> to go
>> back to using URL where ever we use URI (which would
>> mean changing a number of
>> attribute names!).
>> Sigh :-(
>> Carl-Uno Manros
>> Principal Engineer - Advanced Printing Standards - Xerox Corporation
>> 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
>> Phone +1-310-333 8273, Fax +1-310-333 5514
>> Email: firstname.lastname@example.org