quot;
Sent: Tuesday, July 16, 2013 5:32 PM
To: ietf@ietf.org
Cc: The IESG; IETF-Announce
Subject: Announcement improvement (was: Re: Last Call: RFC 2050 to historic)
For the benefits of those (few and far between) IETF participants that haven't
memorized all RFC numbers, it would be great if an
For the benefits of those (few and far between) IETF participants that
haven't memorized all RFC numbers, it would be great if announcement
such as the one below would contain a tiny bit more information about
the document itself.
E.g. just having the title of the document in announcement woul
tnx
Scott
On Jul 10, 2013, at 7:45 PM, Jari Arkko wrote:
>
> Scott,
>
>> is there a reason to not disclose who the individual participant is?
>
> No, but actually that text just came from the standard boilerplate for the
> last call text in these cases. In reality has been several people as
Scott,
> is there a reason to not disclose who the individual participant is?
No, but actually that text just came from the standard boilerplate for the last
call text in these cases. In reality has been several people asking for this to
be done, e.g., SM wrote a document about 2050 and a few
is there a reason to not disclose who the individual participant is?
Scott
On Jul 10, 2013, at 5:39 PM, The IESG wrote:
>
> The IESG has received a request from an individual participant to make
> the following status changes:
>
> - RFC2050 from Best Current Practice to Historic
>
> The supp
