attachment
<html>
<font size=3>I agree that there is no guarantee that
"printer-name" values are unique <br>
even within a domain, but they should be unique as a practical matter so
<br>
that a user can uniquely identify a printer by its
"printer-name" instead of <br>
the URL, at least in a local context.<br>
<br>
There remains the issue of how does anyone determine if two separate SLP
<br>
entries (with different URLs) represent the same output device. I am
<br>
suggesting using a convention that a "printer-name" qualified
by a domain <br>
name and SLP scope uniquely identifies a printer.<br>
<br>
<br>
Bob Herriot<br>
<br>
At 05:02 PM 1/4/99 , Manros, Carl-Uno B wrote:<br>
>Bob,<br>
> <br>
>I welcome this attempt to get a simpler SLP solution and in practice
I think<br>
>we will find few printers that have more than one URI.<br>
>However, your assumption in a) that you could use 'printer-name' to
find out<br>
>whether a printer has several URIs does not<br>
>seem correct. There is no guarantee that "printer-name' values
are unique,<br>
>even within the same domain (at least not according to IPP).<br>
> <br>
>Carl-Uno<br>
><br>
>-----Original Message-----<br>
>From: Robert Herriot
[<a href="mailto:robert.herriot@Eng.Sun.COM%5D" eudora="autourl"><font size=3>mailto:robert.herriot@Eng.Sun.COM]</a><br>
<font size=3>>Sent: Monday, January 04, 1999 4:38 PM<br>
>To: Ira McDonald; imcdonal@sdsp.mc.xerox.com; ipp@pwg.org;
srvloc@srvloc.org<br>
>Subject: Re: IPP> Revised SLP 'printer:' template for
comments<br>
><br>
><br>
>At our Tucson meeting, the IPP group agreed with James Kempf that
there <br>
>should be a separate SLP entry for each URI and that the URI
associated with<br>
><br>
>the entry would be the printer's URI. Ira, I know that you
disagreed with <br>
>this direction.<br>
><br>
>If we stay with this decision, it implies to me that there is <br>
> a) no need for the 'printer-uri-supported'
attribute in the template. It<br>
>can be <br>
> determined by finding all
URI's containing a 'printer-name' with a<br>
>particular value.<br>
> b) 'uri-security-supported' contains the security
supported for the<br>
>associated URI and<br>
> not for other URIs
associated with a printer.<br>
> c) the complexity of two parallel attributes is
eliminated.<br>
><br>
>Bob Herriot<br>
> </font><br>
</html>