Con-call to review the Security draft's normative statements

"Jim Pinkerton" <[email protected]>
Newsgroups gmane.ietf.rddp
Message-ID <E6564B8F86852D46A4E98C485FB33B8F099BB239@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
As was discussed last week at the IETF RDDP WG meeting, the latest
security draft revision
(http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-03.txt)
has changed many of the mitigations in the draft to be normative
statements. In the interest of quickly iterating to a consensus on these
changes, it might be worthwhile doing the first round of iteration on a
con-call.

 

Thus I've set up a conference call on August 26th, 10am-noon PDT,
noon-2pm CDT, 1-3pm EDT, to review any comments people have specifically
around the normative statements made in the spec. There is about zero
normative text before section 7.2.4 (one additional one in section 4.1).
>From there, the general format is explain attack, create normative
counter-measures. If you're short on time, you can just read the
normative counter-measure part. I would propose this meeting *only*
review normative text, to keep it to a tractable amount of time. If you
have other feedback, please either contact the authors directly or send
it to the reflector. If you have feedback on the normative text, if
possible please come with suggested text on how it should be changed.
This will make the call go a lot faster.

 

If you'd like to attend, please send me mail for the conference-call
information. All comers are welcome. Note that this call will not be
used to achieve formal work group consensus - that can only be done by
the chair, on the reflector. Thus not attending (or attending!) the call
does not in any way restrict what you want to bring up on the reflector.

 

 

 

Jim Pinkerton

_______________________________________________
rddp mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/rddp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.