Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice

[Stewart Bryant <[e-mail]>]

On 10/01/2014 01:16, Ines Robles wrote:
> *
>
> Hello,
>
> *
> *
>
> The IESG approvedthe draft-moonesamy-ietf-conduct-3184bis-06 
> <https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/>, 
> 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 foreseenrisks and threats to potential implementers and 
> users. ”
>
> *
Surely the best you can hope for is:

*"..without describing all **of the **actual and potential risks and 
threats to implementers and users that they are aware of."

*The advice is by definition a best effort service.*

*- Stewart*
*
> *
>
> 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 <[e-mail] <mailto:[e-mail]>>
>
>
>        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 <[e-mail]
>     <mailto:[e-mail]>>
>     To: S Moonesamy <[e-mail] <mailto:[e-mail]>>
>     Cc: [e-mail] <mailto:[e-mail]>
>     Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>             (IETF   Guidelines for Conduct) to Best Current Practice
>     Message-ID: <[e-mail]
>     <mailto:[e-mail]>>
>     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
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/ietf
>
>
>     End of ietf Digest, Vol 66, Issue 60
>     ************************************
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html