Document: draft-ietf-deprecate-site-local-02.txt
Reviewer: Scott Brim
Date: March 16, 2004


This document is ready for publication.  If publication is put
off for some other reason, I have two nits, but they should not in
themselves hold it back.

First, please remind me why it is targeted to Proposed Standard?  IIRC
the only reason is to give it the same status as the documents it's
negating (particularly sections of rfc3513 and rfc3484).  Except for
that, this document should be informational or BCP.  I suspect the IESG
has discussed this enough already, but If you are dissatisfied with the
intended status, I suggest flagging it for Discuss.  Otherwise it's a
Yes.

Second, in the Security section, I would add a paragraph reiterating 
of the issues due to ambiguity which were brought up in the preceding
sections.  Leakage, misrouting, etc., are noteworthy security issues.