> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> Alessandro Vesely
> Sent: Monday, February 27, 2012 1:20 AM
> To: [email protected]
> Subject: Re: [marf] Meeting scheduled
> 
> That's the same session as the MILE slot.  In Taipei, Kathleen asked
> whether any MARF participant was present...  I don't know whether she's
> going to repeat that in Paris.  The issue is about a format to marshal
> ARF reports inside IODEF incidents, as John mentioned in
> http://mipassoc.org/pipermail/abuse-feedback-report/2009q3/000264.html

We're not chartered to do any of this work, and we're not aware of any active 
cross-participation, so we didn't list MILE as a scheduling conflict.

> See http://tools.ietf.org/html/draft-vesely-mile-mail-abuse for a
> proposed naked format.  If LIRs are serious about mandatory abuse-
> mailboxes, they may actually need something like that.  Do we have
> hints about how applications can handle xmllized ARF messages?

I haven't heard of any work in this area.  Others?

> > This should be the last time this WG meets as by then all of our
> > deliverables should have completed their IETF Last Calls and be on
> > their way to the IESG.
> 
> No rechartering?  Indeed, it seems we've even done some of the tasks --
> but not all-- that we thought we'd have to recharter for, see
> http://mipassoc.org/pipermail/abuse-feedback-report/2009q4/000463.html

I asked more than once if the group wanted to pick up the reporting-discovery 
draft, but no champion came forward.  I also asked JD's employer if they wanted 
to appoint someone to pick up where he left off, but they weren't able to 
commit the resources.

There was also no consensus to support the idea of reporting general security 
incidents through ARF.

If there are indeed people that want to do those things, the work can be 
resumed as individual submissions or perhaps through APPSAWG after MARF winds 
down.

-MSK
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf

Reply via email to