Re: [perpass] perpass: what next?

[Michael Richardson <[e-mail]>]

Stefan Winter <[e-mail]> wrote:
    > I've tried to bring work to the IETF to create a config file format for
    > EAP; the basic idea being that if IETF created EAP, we should also
    > create a means to communicate EAP *configuration*.

    > I didn't find a spot-on working group to take this to and presented it
    > to opsarea / opsawg instead.

    > There was only a rather mild interest in the draft, it hasn't led to
    > much review activity or a motion to adopt it as a WG draft at this
    > point. I find that a bit disappointing. I'm considering to go AD
    > shopping to publish this in the ISE stream for the lack of a better path
    > to publication.

I agree that we do a poor job here, and I think that we should make this kind
of interaction smoother.  I spent four years working on rfc4332 (OE for IPsec/IKE),
and version 1 was always going to be on the ISE.

    > BTW, the current draft is here; as it happens, it expires today, and
    > honestly I'm wondering if it's worth refreshing it:

    > https://tools.ietf.org/html/draft-winter-opsawg-eap-metadata-01

I would say yes. I was going to ask if there were implementations, and you
clearly have some... Would there be value to deploy this at IETF meeting
networks?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-