Stewart Bryant wrote:
> Generally speaking just getting the slides before the
> slot is difficult enough without specifying a format
> that the author may not normally use.
As a chair, I believe it is my responsibility to either
obtain the presentations as PDF or convert them to PDF
before posting
I don't believe the new charter of ieprep working group belongs in
the IETF... the work that remains belongs somewhere else--probably
the ITU-T.
Let's address this directly.
ITU-T gave us a set of requirements in
[3] "Description of an International Emergency Preference Scheme
(I
> "Fred" == Fred Baker <[EMAIL PROTECTED]> writes:
Fred> The remaining requirements, as I understand them, relate to
Fred> more traditional internet applications: the delivery of
Fred> email within a stated interval, reliable file transfer at a
Fred> stated rate in the presence
Joe:
> 5. Unique Key Names
>
> This section states "the key name MUST NOT be based on the
> keying material itself." 802.11i uses this technique; are
> there vulnerabilities associated with this?
Does this proposed text resolve your concern?
AAA key management proposals require a robust key n
Review of draft-cam-winget-eap-fast-05.txt
Publication Request
---
A request has been made from an individual submitter to publish EAP FAST
as an Informational RFC. The document has gone to IETF last call:
http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg03074.html
On Wed, 15 Nov 2006, Fred Baker wrote:
> We also specifically addressed their requirements (in tsvwg) operationally:
>
> >http://www.ietf.org/rfc/rfc4594.txt
> >4594 Configuration Guidelines for DiffServ Service Classes. J.
> > Babiarz, K. Chan, F. Baker. August 2006. (Format: TXT=144044 bytes
