On March 9, 2009 Alan DeKok wrote...
Security Section:
There are good reasons to provision USM access so supplement with
AAA-based access, however.
NIT: This doesn't appear to be a sentence.
Yeah. Let's see what that was supposed to say... I think it's:
There are good
It would be great if the ietf list could be reminded when the
new version of the rather excellent xml2rfc tool is issued, so
we don't need to keep checking back for it.
It would be even *better* if the cutoff date for acceptance of submissions
in the old format was conditioned upon having an
Glen Zorn writes...
There's just one big difference: EAP is, in fact, a separate protocol,
distinct from RADIUS.
We're talking about EAP messages tunneled in RADIUS Attributes. That's what
qualifies for the opaque blob exception.
We're talking about RADIUS attributes here, and the document
Glen Zorn writes...
I'm quite aware of that if, in fact, the attributes were opaque
data that passage would certainly cover it. However, it doesn't
appear that either the Location-Information nor the Location-Data
Attribute is actually opaque.
I've offered similar comments early on in the
This is still a problem. Please turn off whatever logging or debugging is
causing the servers to drop connections, and refuse to accept reconnects
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Are we a victim of our own success here, i.e. is wider usage causing the
server overload?
In both sessions in the afternoon that I attended (ipfix, opsawg) people
who were on jabber and listening to audio streams complained about
repeated interruptions in the audio feed.
Harald Tveit Alvestrand writes...
Can't believe nobody else posted first
http://youtube.com/watch?v=_y36fG2Oba0
LOL. This is priceless...
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
