My suggestion isn't to copy them to ietf@xxxxxxxx, but, rather, to copy them to ietf-announce@xxxxxxxx. b On Wed, Feb 26, 2020 at 2:02 PM Jay Daley <jay@xxxxxxxx> wrote: > > Thanks Barry > > On 27/02/2020, at 10:58 AM, Barry Leiba <barryleiba@xxxxxxxxxxxx> wrote: > > On Wed, Feb 26, 2020 at 4:59 AM Michael Richardson > <mcr+ietf@xxxxxxxxxxxx> wrote: > > > The ietf-lastcall split has been good for ietf-announce volume, but > > > But here's the thing: That split should have not affected the volume > on ietf-announce *at all*. It should have reduced volume on > <ietf@xxxxxxxx>, which is a very different thing. This isn't the > message thread to discuss that further, but I mention it here to lead > into agreement with some other comments: > > I believe that having a new "rfp-announce" list is a fine thing *if* > RFC announcements are posted to *both* ietf-announce and rfc-announce. > That should satisfy all the concerns here: those who subscribe to > ietf-announce need to change nothing and will still get RFP > announcements, and those who only want RFC announcements and not the > other stuff can subscribe only to rfp-announce -- it's an individual > choice. > > > In order to close this thread I will cc: ietf@ietf on all posts to rfp-announce, which is trivial to do. > > Jay > > > Barry > > > -- > Jay Daley > IETF Executive Director > jay@xxxxxxxx > +64 21 678840 >
