Re: [OSPF] OSPF WG Closing (work to LSR)

[Abdussalam Baryun <abdussalambaryun@xxxxxxxxx>]

I did not expect this is the way WG closes in IETF, is there a clear procedure or best ways of closing WGs?

 IMO, it is not a right way to close.

AB

On Sat, Mar 3, 2018 at 12:16 AM, <ospf-owner@xxxxxxxx> wrote:

The OSPF WG has closed. Relevant discussions are continuing in the
Link-State Routing (LSR) WG. Please resend your message to
lsr@xxxxxxxx.

my subject is about closing OSPF not LSR, 

---------- Forwarded message ----------
From: Abdussalam Baryun <abdussalambaryun@xxxxxxxxx>
To: Alia Atlas <akatlas@xxxxxxxxx>
Cc: OSPF List <ospf@xxxxxxxx>
Bcc: 
Date: Sat, 3 Mar 2018 00:16:12 +0200
Subject: Re: [OSPF] OSPF WG Closing (work to LSR)

I don't think it should be closed,

AB

On Thu, Mar 1, 2018 at 8:53 PM, Alia Atlas <akatlas@xxxxxxxxx> wrote:

As I expect you have seen, the charter for the Link-State Routing (lsr) WG has been approved and the lsr WG now exists.  

All subscribers to the ospf mailing list have been subscribed to the lsr mailing list.

OSPF WG drafts that are already in the RFC Editor's queue will remain as being

published from the OSPF WG - but follow-up will be to the lsr mailing list.

All OSPF WG drafts have been migrated to the lsr WG and appear on the data-tracker.

In the LSR datatracker (on the About tab under Additional Links), there are links to both

the OSPF and ISIS datatracker, so that published RFCs and  individual drafts can easily be located.

I would like to again thank Abhay Roy for his many years of service as OSPF WG Chair.

Regards,

Alia

_______________________________________________
OSPF mailing list
OSPF@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ospf