"However it is to be noted that there is an expectation that no one
shall ever knowingly contribute advice or text that may affect the
security of the Internet without describing all known or foreseeable
risks and threats to potential implementers and users."
And the new text:
However it is to be noted that there is an expectation that no one
shall ever knowingly contribute advice or text that may adversely
affect the security of the Internet without describing all known or
foreseen risks and threats to potential implementers and users.
Please note, that due to this new version, the AD give until Tuesday next week to provide comments before send the draft to the RFC Editor.
Thanks and Regards,
Ines Robles.
Hello,
The IESG approved the draft-moonesamy-ietf-conduct-3184bis-06, including these new changes:
Section 3 (foreseeable was replaced by foreseen)
OLD:
“However it is to be noted that there is an expectation that no one shall ever knowingly contribute advice or
text that may affect the security of the Internet without describing all known or foreseeable risks and threats to potential implementers and users. ”
NEW:
“However it is to be noted that there is an expectation that no one shall ever knowingly contribute advice or
text that may affect the security of the Internet without describing all known or foreseen risks and threats to potential implementers and users. ”Section 4:
The word "adversely" which was added to the last sentence in Section 4.
Please note, that due to this new version, the AD give until Tuesday next week to provide comments before send the draft to the RFC Editor.
Thank you and Kind Regards,
Ines Robles.
2013/11/8 <ietf-request@xxxxxxxx>
5. Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
(IETF Guidelines for Conduct) to Best Current Practice
(Brian E Carpenter)
------------------------------
Message: 5
Date: Sat, 09 Nov 2013 08:33:14 +1300
From: Brian E Carpenter <brian.e.carpenter@xxxxxxxxx>
To: S Moonesamy <sm+ietf@xxxxxxxxxxxx>
Cc: ietf@xxxxxxxx
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
(IETF Guidelines for Conduct) to Best Current Practice
Message-ID: <527D3C7A.1060200@xxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
That works for me.
Thanks
Brian
On 09/11/2013 07:03, S Moonesamy wrote:
> Hi Brian,
> At 18:58 07-11-2013, Brian E Carpenter wrote:
>> Fair enough. But people do need to respect the shortage of time. How
>> about
>> "Working Group meetings run on a very limited time schedule,
>> and sometimes participants have to limit their questions.
>> The work of the group will continue on the mailing list, and
>> questions can be asked and answered on the list."
>
> How about:
>
> IETF participants read the relevant Internet-Drafts, RFCs, and
> email archives beforehand, in order to familiarize themselves
> with the technology under discussion. Working Group sessions
> run on a very limited time schedule, and sometimes participants
> have to limit their questions. The work of the group will
> continue on the mailing list, and questions can be asked and
> answered on the mailing list. It can be a challenge when
> attending a new working group without knowing the history of
> longstanding Working Group debates. Information about a working
> group including its charter and milestones is available on the
> IETF Tools web site [TOOLS] or from the working group chair.
>
> Regards,
> S. Moonesamy
> .
>
------------------------------
_______________________________________________
ietf mailing list
ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
End of ietf Digest, Vol 66, Issue 60
************************************